Jon Westfall
07-10-2007, 01:38 AM
<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/andrewarnottm...-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 />Andrew Arnott has some helpful tips on how to make applications that don't fall apart like a cheap card table. Check it out if you're trying to make your apps speedy, responsive, and non-deadly.