Kris Kumar
07-09-2007, 03:30 PM
<div class='os_post_top_link'><a href='http://blogs.msdn.com/andrewarnottms/archive/2007/07/02/how-to-write-an-especially-precarious-app-on-net-compact-framework.aspx' target='_blank'>http://blogs.msdn.com/andrewarnottms/archive/2007/07/02/how-to-write-an-especially-precarious-app-on-net-compact-framework.aspx</a><br /><br /></div><i>"As the .NET Compact Framework developers work to add features, fix bugs, and refactor code, we often have to determine whether a given change could break existing customer code. The ideal is that NetCF 3.5 will run all apps that ran on NetCF 2.0 and 1.0. We run hundreds of apps and many, many tests before shipping each product to check backward compatibility. The .NET Framework (both desktop and CF) makes heavy use of internal classes to allow us the freedom to change the internals of the framework without breaking customer code. But there are still ways that customers can write apps that may break on future versions."</i><br /><br />A must read for every .NET Framework application developer. Andrew Arnott is providing tips that will help the developers write code that will work well with the current and future versions of the .NET Compact Framework. In case you are not familiar with .NET CF, then you should check out the <a href="http://msdn2.microsoft.com/en-us/netframework/aa497282.aspx">Getting Started</a> guide on MSDN, and <a href="http://samples.gotdotnet.com/quickstart/compactframework/">these tutorials.</a>