If broken it is, fix it you should

Using the powers of the debugger to solve the problems of the world - and a bag of chips    by Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft)

June, 2009

  • If broken it is, fix it you should

    First look at debugging .NET 4.0 dumps in Visual Studio 2010

    I know that for a lot of you this is a bit far into the future, but I thought it would be nice to run through a few of my lab scenarios to show off some of the new features in Visual Studio 2010.  I am sure that I will miss a bunch of cool features here as this post is just based on my first experience with this, but I will likely post more about these features as we get closer to RTM.  As we are only in Beta, anything and everything may change before RTM and the below is just based on...
  • If broken it is, fix it you should

    A case of lost session variables when using out of process session state

    Recently I had a case where the customer had an issue with session variables.  The claim was that if they use in-proc session state their session variables would work just fine, but if they changed the session mode to stateserver in web.config their sessions were lost. <sessionState mode="StateServer" cookieless="UseCookies" stateConnectionString="tcpip="/> When looking at bit closer at the repro, it wasn’t really all session variables that...
  • If broken it is, fix it you should

    Visual Studio 2010 .net debugging resource

    If my post on dump debugging in VS 2010 piqued your interest, here is a list of a number of other new debugging features coming up in 2010 http://blogs.msdn.com/ms_joc/archive/2009/05/27/dev10-beta1-free-at-last.aspx I for one will be following the blog to get the scoop… On a related note, John Robbins also wrote a nice post about historical debugging in VS2010, I haven’t tried it yet but I can already see a number of ASP.NET scenarios where it can be applied. http://www.wintellect...
Page 1 of 1 (3 items)