.NET Blog

Free. Cross-platform. Open source. A developer platform for building all your apps.

Preview of Code Contract Tools Now Available
Preview of Code Contract Tools Now Available
CLR TeamMarch 4, 2009Mar 4, 200903/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
Resource Manager and .Net Interaction with ServiceControlManager
CLR TeamMarch 1, 2009Mar 1, 200903/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 Inside Out – Isolated Storage in Silverlight 2
CLR TeamFebruary 20, 2009Feb 20, 200902/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 Inside Out – Handling Corrupted State Exceptions
CLR TeamFebruary 20, 2009Feb 20, 200902/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
Why catch(Exception)/empty catch is bad
CLR TeamFebruary 19, 2009Feb 19, 200902/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 ...
Why catch(Exception)/empty catch is bad
Why catch(Exception)/empty catch is bad
CLR TeamFebruary 19, 2009Feb 19, 200902/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 ...
Catch, Rethrow and Filters – Why you should care?
Catch, Rethrow and Filters – Why you should care?
CLR TeamFebruary 5, 2009Feb 5, 200902/5/09
 A very common pattern in the usage of managed exception handling is that of catching an exception, inspecting it's type and rethrowing it once you realize it was not the exception you wanted to handle. Below is such an example (and should be avoided in preference to another approach described further below in the writeup) that uses ...
Catch, Rethrow and Filters – Why you should care?
Catch, Rethrow and Filters – Why you should care?
CLR TeamFebruary 5, 2009Feb 5, 200902/5/09
 A very common pattern in the usage of managed exception handling is that of catching an exception, inspecting it's type and rethrowing it once you realize it was not the exception you wanted to handle. Below is such an example (and should be avoided in preference to another approach described further below in the writeup) that uses ...
Catch, Rethrow and Filters – Why you should care?
Catch, Rethrow and Filters – Why you should care?
CLR TeamFebruary 5, 2009Feb 5, 200902/5/09
 A very common pattern in the usage of managed exception handling is that of catching an exception, inspecting it's type and rethrowing it once you realize it was not the exception you wanted to handle. Below is such an example (and should be avoided in preference to another approach described further below in the writeup) that uses ...
Understanding the Binder – Part 1
Understanding the Binder – Part 1
CLR TeamJanuary 29, 2009Jan 29, 200901/29/09
 This is an introductory post on the internals of CLR Binder.     What does the Binder do? CLR's Binder is a piece of code that, when given an assembly name, determines where the assembly is and binds to it. So how does the Binder locate assemblies? Let's assume that you are loading an assembly (let’s ...