Chat Question: What extension to use in what situation

DotNetKicks.com — Fri, 18 Apr 2008 18:39:01 GMT

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

Chat Question: What extension to use in what situation

Website Magazine — Fri, 18 Apr 2008 21:18:19 GMT

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

Chat Question: What extension to use in what situation

Website Magazine — Tue, 20 May 2008 06:35:53 GMT

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

re: Chat Question: What extension to use in what situation

daveblack — Tue, 02 Jun 2009 22:31:39 GMT

Additional info on IIS & 32-bit vs. 64-bit...

quoting from an article on Tess's blog:

<quote>

By default when you run IIS on a 64-bit machine you will still be running a 32-bit w3wp.exe, so apart from a few differences, like being able to use 4 GB virtual bytes instead of 2 GB virtual bytes the difference in debugging an issue on 32-bit vs. 64-bit is not that big. You will still be debugging with a 32-bit debugger and the memory will be aligned the same as in any 32-bit process on a 32-bit system.

As a matter of fact, something that is very important to point out, is that if you happen to use the 64-bit version of windbg.exe and the debugging tools for windows you will create dumps that are virtually unusable for debugging managed issues.

However if you have installed 64-bit IIS it's a bit different. If that is the case you need to take special care to use the 64-bit debuggers and the 64-bit version of sos.dll etc. or else you will not see anything at all.

</quote>

from http://blogs.msdn.com/tess/archive/2007/08/09/asp-net-memory-issue-high-memory-usage-in-a-64bit-w3wp-exe-process.aspx

re: Chat Question: What extension to use in what situation

Tom — Wed, 03 Jun 2009 17:27:41 GMT

That is very true, that is why in the table I talk about the process version, not really the OS version. Be sure to know which one you are running.