ASP.NET and SOS

DotNetKicks.com — Tue, 25 Mar 2008 17:07:42 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: ASP.NET and SOS

Eric Pearson — Tue, 25 Mar 2008 18:37:18 GMT

After working on that sp1 issue with you in support, I would love an easier way to inspect objects: such as DumpObj automatically expanding or formatting datetimes and valuetypes and strings inline so you can get a better view of an object's contents at a glance.

re: ASP.NET and SOS

Gordon Weakliem — Tue, 25 Mar 2008 18:50:16 GMT

I do miss !dumpaspnetcache, Tess posted a workaround, but it's not especially fun.

http://blogs.msdn.com/tess/archive/2006/01/26/asp-net-memory-how-much-are-you-caching-an-example-of-foreach.aspx#1842670

re: ASP.NET and SOS

wisemx — Tue, 25 Mar 2008 18:59:53 GMT

At this point I'd say yes, the IIS7 methods.

If more ASP.NET developers see this:

http://mtaulty.com/communityserver/blogs/mike_taultys_blog/archive/2004/08/06/4685.aspx

...They may be able to better answer your question. ;-)

re: ASP.NET and SOS

Pawel Pabich — Wed, 26 Mar 2008 16:24:03 GMT

It would be great to have UI that lets you browse managed heap but I suppose it is more Windbg than SOS feature request.

re: ASP.NET and SOS

Tom — Wed, 26 Mar 2008 16:34:18 GMT

Like what kind of UI? Browse the managed heap as in like graphically? I have had a few ideas around this myself, but what kind of visual were you thinking?

ASP.NET Tips: Debugger command you may not know about - aspxpages

ASP.NET Debugging — Thu, 27 Mar 2008 20:26:15 GMT

So there are a lot of useful commands in sos that you may not know about.  I am going to hit on

ANSWER: POP QUIZ: What to do next? - part 1

ASP.NET Debugging — Mon, 31 Mar 2008 20:56:23 GMT

So we didn't get much more on this one, so I'll go ahead and show how we find out what is going on here. 

re: ASP.NET and SOS

Ron — Tue, 01 Apr 2008 22:36:35 GMT

I really miss the -gen option on the dh command. I used the -gen with -stat a lot in the 1.x version of sos.

re: ASP.NET and SOS

Ron — Tue, 01 Apr 2008 22:47:38 GMT

I wasn't aware of the !aspxpages command until I read your blog. I can see how it could be extremely beneficial in troubleshooting web apps.

Chat Question: What extension to use in what situation

ASP.NET Debugging — Fri, 18 Apr 2008 18:34:14 GMT

So we have a bunch of debugger extensions that we need to use depending on the situation.  So here

Why are some commands missing in sos for 2.0 compared to sos for 1.1?

If broken it is, fix it you should — Wed, 30 Apr 2008 09:27:22 GMT

This question that I got from a reader is something that I get asked pretty frequently... "I met a small

re: ASP.NET and SOS

daveblack — Tue, 02 Jun 2009 22:20:28 GMT

I have downloaded and installed the latest version of the Debugging Tools for Windows (ver. 6.11.0001.404). I've been using WinDBG with SOS and had been getting "Doesn't work in 2.x" messages for most of the SOS commands. I assumed that I should be using the version installed with the Debugging Tools instead of the one with the Framework since that version is the newest and is much larger in size (thinking they've added a bunch of new functionality).

If I load the version of SOS that works with .NET 2.0, it doesn't have the newer commands in it that the version for 1.x does. Thus, I find that if I load the version with .NET 2.0, I get "No export 'commandNameHere' found".

some examples:

GCRef

DumpASPNETCache

DumpDataTables

DumpDynamicAssemblies

DumpHttpRuntime

DumpXmlDocument

SearchStack

CLRUsage

FindDebugModules

FindTable

What is most frustrating is that new commands are being added to the .NET 1.x version but nothing is being done with SOS for .NET 2.0+

Why the disconnect and what is being to provide these newer commands to the .NET 2.0+ version?

TIA

Dave

re: ASP.NET and SOS

Tom — Wed, 03 Jun 2009 17:28:52 GMT

Dave,

We are currently working on that exact issue. We are very aware of the disconnect and are working to get that resolved soon.

re: ASP.NET and SOS

daveblack — Wed, 03 Jun 2009 18:12:36 GMT

Tom,

Thank you much for your reply : )

1. Is there any general timeframe that the update would be available?

2. Will it be available before the release of VS2010?

3. Would the update be packaged as part of the Debugging Tools for Windows or as a SP for VisualStudio? It is confusing to have the two versions and one of them should be deprecated *or* they should always be kept in sync.

re: ASP.NET and SOS

Tom — Wed, 03 Jun 2009 19:01:33 GMT

Dave,

There isn't a timeframe yet, but we hope to have something soon. We are also beginning to talk about doing similar things for 4.0. The way it works is the CLR development team releases the SOS that comes with the framework. Then we work on what we can do on top of that. I am hoping for 4.0 to change it quite a bit but we will see how that works out.

re: ASP.NET and SOS

daveblack — Wed, 03 Jun 2009 22:34:25 GMT

Thank you for your efforts to resolve the issue!

Hopefully, things will be a little easier for those of us who heavily rely on SOS when you need to bring out the "big guns".

Is your blog the place to watch for posting about a new release or is there a blog for the WinDBG/SOS team?

TIA

re: ASP.NET and SOS

Tom — Wed, 03 Jun 2009 22:50:24 GMT

This blog is probably the best, I'll be letting people know as soon as anything happens.