Linked by Thom Holwerda on Mon 6th Oct 2008 10:37 UTC, submitted by John Mills
Permalink for comment 332671
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-06
It all depends on whether the original program uses P/Invoke calls to native code dlls, or uses APIs that aren't supported yet. If not, there is a good chance that the binaries will run without change or recompile.
In the case of Paint.NET you are out of luck for now: There are a lot of P/Invoke calls but almost everything else works as of the new release - it's even shown in the release notes. It's funny that most everyone uses Paint.NET for an example when they are asking this question.
There aren't that many popular .NET apps for Windows either, or Java, or interpreted languages (the aforementioned are not interpreted). That's to be expected though. As with any platform in wide use, most Windows apps are not the "popular" type: They are either internal business apps, or tiny utilities that wouldn't need to be ported.