Kris Kumar
12-19-2005, 08:00 PM
<div class='os_post_top_link'><a href='http://blogs.msdn.com/stevenpr/archive/2005/12/12/502908.aspx' target='_blank'>http://blogs.msdn.com/stevenpr/archive/2005/12/12/502908.aspx</a><br /><br /></div><i>"In the last few weeks I've been working on a series of posts that describes why various design decisions were made when building the .Net Compact Framework CLR. In this first post, I describe the environmental factors that have influenced the design and provide an overview of how the CLR manages memory. Subsequent posts will follow with details on the main design tenants of the JIT compiler, garbage collector, and class loader as well as information about how to analyze the memory usage of your Compact Framework application. Throughout the series I'll be noting design decisions made when building the Compact Framework's CLR that are quite different than those made when building the CLR in the full .Net Framework."</i><br /><br />Steven Pratschner has written a <i>comprehensive</i> tutorial on .NET Compact Framework CLR. You can check out the three part tutorial over here:<br />• <a href="http://blogs.msdn.com/stevenpr/archive/2005/12/12/502908.aspx">Part 1: Overview and Background</a><br />• <a href="http://blogs.msdn.com/stevenpr/archive/2005/12/12/502978.aspx">Part 2: JIT Compiler Design Considerations</a><br />• <a href="http://blogs.msdn.com/stevenpr/archive/2005/12/14/503818.aspx">Part 3: Garbage Collector Heap Management</a>