Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Andrew Pardoe   (RSS)

How to Make the Most of Your .NET Server Code

One of our team’s field engineers recently sent a link to a Channel 9 video: Steve Michelotti of e.magination on High Performance Web Solutions . This company built a 64-bit web server that handles over 3 billion transactions a day and guarantees a 250
Posted by CLRTeam | 2 Comments
Filed under: ,

Getting more information than the exception class provides

We recently had a question about how to get more information than an exception’s type provides. The developer was trying to copy a file and didn’t know why the copy was failing. File copies can fail for many reasons, almost all of them what Eric Lippert

More Channel 9 videos

We have more Channel 9 videos from the CLR team for your enjoyment! The Base Class Libraries ( BCL ) team talks about some of the new features in the next version of BCL over here . We have Maoni Stephens and Andrew Pardoe talking about Background Garbage

ThreadAbortException

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:

CLR Inside Out - Handling Corrupted State Exceptions

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
Posted by CLRTeam | 1 Comments

Why catch(Exception)/empty catch is bad

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.
 
Page view tracker