The Design of the .Net Compact Framework CLR, Part III: GC Heap Management

Here’s Part III of the series on the design of the .Net Compact Framework CLR.  Previous posts in this series provided an overview of how the CLR manages memory and described the basic design tenants of the JIT compilers: Part I, Overview and Background Part II, Jit Compiler Design Considerations This post focuses on the…

5

The Design of the .Net Compact Framework CLR, Part II: JIT Compiler Design Considerations

This is the second in a series of posts describing the design of the .Net Compact Framework CLR.  If you missed Part 1, you can find it here.  This installment describes the basic design tenants of the .Net Compact Framework JIT compilers. —- The primary design difference, at least with respect to memory usage, between the .Net Compact…

1

The Design of the .Net Compact Framework CLR, Part 1: Overview and Background

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…

12

Why Upgrade to Version 2.0 of the .Net Compact Framework?

  Much has been written about the new technical features available in version 2 of the .Net Compact Framework.  In this post, I’ve tried to take a “higher level” approach by describing the product in terms of the benefits it can bring to a organization.  This post is targeted at those who are currently analyzing…

1

Diagnosing Marshaling Errors using Interop Logging

In a previous post I described how the Loader Log can be used to help diagnose problems such as assembly load failures, version mismatches and so on (http://blogs.msdn.com/stevenpr/archive/2005/02/28/381744.aspx ).  Another critical element of our new diagnostics feature set in Whidbey is Interop Logging. Interop logging was added in response to the huge number of questions…

4

Update on “Using POOM with .Net Compact Framework Whidbey”

Last summer I wrote a post about how to access the PocketOutlook Object Model (POOM) using the Beta1 build of the .Net Compact Framework (http://blogs.msdn.com/stevenpr/archive/2004/08/05/209390.aspx ).  A few things have changed since then that make this scenario even easier. Specifically, last summer’s post included instructions for registering the POOM type library on your device.  This…

3

Better Diagnostics in Whidbey: Loader Logging

If you’ve spent much time developing applications with version 1 of the .Net Compact Framework, you’ve likely been frustrated at times by the lack of tools to help you diagnose problems in your applications.  Even common errors, like the failure to find an assembly are hard to diagnose, much less more complex problems like memory…

10

.Net Compact Framework: Versioning, Strong Names and the Global Assembly Cache – Part 2

Last summer I posted an article that described the basic differences between the .Net Compact Framework and the full .Net Framework with respect to versioning and deployment (see http://blogs.msdn.com/stevenpr/archive/2004/06/30/170289.aspx ).  Recently, I’ve come across a few other topics related to assembly loading in which our design differs from that of the full .Net Framework.  This…

6