.NET Blog

ThreadAbortException

CLR Team April 28, 2009 Apr 28, 2009 04/28/09

 System.Threading.ThreadAbortException is just plain weird. For instance, most exceptions happen because of something code did on its own thread: even asynchronous exceptions are caused by something your code did on the current thread. (Note for the nitpickers: gamma rays can cause a bit in memory to flip randomly, bringing about ...

CLR Inside Out – Optimizations In .NET Framework 3.5 SP1

CLR Team April 6, 2009 Apr 6, 2009 04/6/09

The new installment of the “CLR Inside Out” column in MSDN magazine is now available on line.  This month we have an article from Surupa Biswas on Optimizations In .NET Framework 3.5 SP1. You can find a list of all “CLR Inside Out” articles here.  As always, please let us know if you have topics you’d...

MIX09 talk on Core CLR

CLR Team March 26, 2009 Mar 26, 2009 03/26/09

 For everyone who attended MIX this year, we hope it was a lot of fun. Brandon from our team, gave a talk on "Going Inside Microsoft Silverlight: Exploring the Core CLR" at MIX09 last week. The talk covers how the desktop CLR was slimmed down to be used for Silverlight, and in the process, covers Core CLR's architecture (...

Exceptions out of Fault/Finally

CLR Team March 23, 2009 Mar 23, 2009 03/23/09

 Assumption: This write-up assumes that you are familiar with the managed exception handling constructs (e.g. catch, filter, fault, finally). If not, you may want to read this and also refer to the CLI specification. Managed exception handling exposes constructs to handle an exception (e.g. catch and filter blocks) and also to ...

New TlbImp Release on CodePlex – Full Customization of Interop Assemblies

CLR Team March 19, 2009 Mar 19, 2009 03/19/09

It has been a few months since our last release of TlbImp on CodePlex. We recently released a new version of TlbImp – please visit the Codeplex page for this tool to find out more. In this release, we’ve introduced two major features: 1. Ruled-based customization of interop assemblies 2. TlbImp regression test tool Ruled-based ...

Preview of Code Contract Tools Now Available

CLR Team March 4, 2009 Mar 4, 2009 03/4/09

We’ve mentioned Code Contracts over on the BCL Blog a few times now, but never yet on the CLR Blog.  Basically, Code Contracts are a way to add preconditions, post-conditions, and object invariants to your code.  The goal is to help you catch developer errors earlier in the cycle.  In my Introduction to Code Contracts post...

Resource Manager and .Net Interaction with ServiceControlManager

CLR Team March 1, 2009 Mar 1, 2009 03/1/09

Kim Hamilton has a couple of excellent posts on the BCL Team blog. In the first post on Working with the ResourceManager, Kim talks about the basics of resource generation, constructing a ResourceManager and how resource fallback works. The post also covers debugging resource loading failures using Fusion logs, Reflector and Resview.  ...

CLR Inside Out – Isolated Storage in Silverlight 2

CLR Team February 20, 2009 Feb 20, 2009 02/20/09

  The March installment of the “CLR Inside Out” column in MSDN magazine is now available on line.  This month we have an article from Justin Van Patten on Isolated Storage in Silverligth 2. You can find a list of all “CLR Inside Out” articles here.  As always, please let us know if you ...

CLR Inside Out – Handling Corrupted State Exceptions

CLR Team February 20, 2009 Feb 20, 2009 02/20/09

  As Andrew pointed out in his recent post, the February installment of the “CLR Inside Out” column in MSDN magazine is now available on line.  This month we have an article from Andrew Pardoe on Handling Corrupted State Exceptions.You can find a list of all “CLR Inside Out” articles here.  As ...

Why catch(Exception)/empty catch is bad

CLR Team February 19, 2009 Feb 19, 2009 02/19/09

  You’ve seen the advice before—it’s not a good programming practice to catch System.Exception. Because managed exceptions are hierarchical, catching the top of the hierarchy—e.g., catch(Exception)—is an easy way to make sure that you catch all exceptions.  But do you really want to catch all ...