|
| |
|
Warning to developers: a monkey with its eyes closed can disassemble Microsoft .NET January 17, 2009 [General] | By Edward J. R. Microsoft employees and Microsoft MVPs don't have to break even, they can say whatever sounds good to Microsoft, they live in their own reality distortion field. We however are obliged to tell how it is, even if given story is not positive towards Microsoft. Soon Microsoft will launch Skymarket (i.e. Windows Mobile app store) and several new developers might be interested in developing for Windows Mobile. However for them to avoid disappointment we must reveal one dirty secret of Microsoft technologies: While Microsoft is touting their .NET technology as a very effective way of writing programs for various Microsoft platforms, the reality is that writing commercial applications for Windows Mobile in .NET is a suicide, as one of our readers writes in a comment: .Net is great in so many ways but for commercial apps? No way! Anybody can just look at your source code. A high end obfuscator will help a lot but any determined hacker will fix your code in less than a day. I know this from sad experience despite spending $1000s on anti-piracy and obfuscation tools. Unless you wish to make your code 'open source' then maybe give .Net a wide birth. Note: the only way to protect intellectual property of .NET applications is to use them for writing web applications, because then the code resides on server only. Conclusion: if you intend to develop commercial software for Windows Mobile, then forget .NET, and use instead native technologies like C. Note also that iPhone apps are written in native code and this problem does not exist there at all. If you plan on developing Windows Mobile applications with Skymarket in sight, then be prepared for 1-day delay after which your competitors will copy your functionality and place their own apps with the same functionality in the Skymarket - if you would be foolish enough to use .NET technology of Microsoft. The reality is that Microsoft has completely failed to protect intellectual property of software written in .NET and this may also damage partially future of Windows Mobile.
|
| ||||||
| |