Latest Microsoft Blogs

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 my own impressions so there may be other better ways of doing things. Why debug dumps with Visual Studio .NET I love WinDbg and will probably continue using it for many years to come since it is a very simple and clean and powerful debugger.  I...

There’s been close to 25 000 downloads of the buggy bits lab set , YAY!!! :)  but now I think it’s time to expand it a bit with some new labs.  I have a few different issues in mind but I wanted to check in and see if there is something specific you want to see in the new lab set.  I know that the first request I’ll probably get is to include something about COM debugging or debugging RCW/CCW leaks and I might do that, but I just want to say that I am struggling a bit with this.  Just for fun I installed VB 6.0 the other day to create some nasty COM component, but it has just been so long that I’ve forgotten how to write code without the VS.NET intellisense :) you don’t really realize how good it is to have something until...

... and here are the slides for the interactive session Read More...

I still have to figure out a way to host the video from the break-out session but until then, here are the slides for my presentations (attached). And here are a list of some of the tools and resources I used for the presentations Tool/Resource Comment Download Link Debugging Tools for windows Windbg, adplus etc. http://www.microsoft.com/whdc/devtools/debugging/default.mspx Debug Diag 1.1 Analyzes dumps, good for native memory leaks http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en Cmdtree Command and textfile to get a treeview with commands in windbg http://www.wintellect.com/CS/blogs/jrobbins/archive/2008/09/17/windbg-cmdtree-file-that-eases-some-sos-pain.aspx Tinyget Poor mans...

Following my post about how to troubleshoot a low CPU performance issue with VSTS Test, I will now do the same for lab 4 where we have high CPU in GC. The scenario is pretty similar in that we have a page ( http://localhost/BuggyBits/AllProducts.aspx ) that seems to be taking a lot of time to execute.  We also see that the w3wp.exe process sits at very high CPU ~100% during the time this page executes. Using Windbg in the lab, we saw that the issue here was that we were concatenating a very large string in a loop.  This was generating a lot of full collections since we were constantly exhausting the large object heap, causing us to spend a lot of time in the GC.  Check out the review for Lab 4 for more details on the issue. What...

I know that perhaps not that many of you know Swedish, but for those of you who do, you might want to check out Michael Deurell’s nice screen casts about how to use visual studio test system to troubleshoot the issues in the buggybits labs along with some windbg fun…  His screen casts are called “Fräschast i Bandhagen”, just love that name (unfortunately doesn’t translate that well to English:)) http://blogs.msdn.com/deurell/archive/2008/09/30/debugga-i-produktion-eller-testa-bort-i-utveckligsfas.aspx Laters, Tess Read More...

I know I'm a little late in the game, but I decided that after vacation it was finally time for me to install Windows 2008 on my Vista box and play around with some of the IIS 7 features like Failed Request Tracing (known as FRT or FREB) and the appcmd tool. I wanted to show you an alternative way of troubleshooting Lab 1 (hang scenario) from my Debugging Lab series using Failed Request Tracing and appcmd so here are some things I will go through in this post Setting up failed request tracing Listing executing requests with appcmd Using Page.Trace with failed request tracing Setting up different FREB rules and looking at the differences between them Short notes about failed request tracing Failed request tracing comes with IIS7. It works...

We have reached the end of the .NET Debugging Demos series. And we are going to end it with a review of the last memory leak lab. I am interested to get feedback, either in comments or through email in the contact me section, on what you liked, what you didn't like. If you felt that it was worth your while etc. so I know if there is an interest in possibly doing similar lab series in the future. It will probably be a while before I would post a new series but if there is interest at least I can start thinking about it. If that is the case, let me know what you thought was missing from this one so that I can put some good scenarios in the next one. Previous demos and setup instructions If you are new to the debugging labs, here you can find...

This is the last debugging lab in the .NET Debugging Demos series. By now you should have the basics down for troubleshooting hangs, perf issues, memory leaks and crashes in .net applications. Hope you have enjoyed your debugging sessions. The last one in the series is a managed memory leak caused by holding on to resources in an unexpected way. Since it is the last one I have tried to make the questions a little bit less leading than the previous ones:) Previous demos and setup instructions If you are new to the debugging labs, here you can find information on how to set up the labs as well as links to the previous labs in the series. Information and setup instructions Lab 1: Hang Lab 1: Hang - review Lab 2: Crash Lab 2: Crash - review Lab...

Since it took me so long to get Lab 6 out the door i'll post the review right away... After this we only have one memory leak lab to go before you have gone through the whole lab set. Previous demos and setup instructions If you are new to the debugging labs, here you can find information on how to set up the labs as well as links to the previous labs in the series. Information and setup instructions Lab 1: Hang Lab 1: Hang - review Lab 2: Crash Lab 2: Crash - review Lab 3: Memory Lab 3: Memory - review Lab 4: High CPU hang Lab 4: High CPU hang - review Lab 5: Crash Lab 5: Crash - review Lab 6: Memory leak Problem description: We have started getting out of memory exceptions on the buggy bits site and we have been able to determine a scenario...