LPE

A lot of people have problems with this specific topic, and as always, I blame Microsoft ‘couse this topic is seriously unintuitive.

First off, installing MVC 2 aswell as .NET 4.0.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7aba081a-19b9-44c4-a247-3882c8f749e3

After installation, follow these easy steps.
1. Right click your website, choose properties
2. Click the tab called “Home Directory”
3. Choose “Configuration”
4. At the wildcard part choose “Insert”
5. Find the file called aspnet_isapi.dll on your computer, usually located at C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
6. DO NOT forget to uncheck “Verify that file exists”
7. Go back to the IIS 6 Manager and choose Webservice Extensions
8. Make sure your .NET Framework has status “Allowed”

If you’re thinking about running .mvc file endings or any other thoughts, use these guides:
http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx
http://blog.stevensanderson.com/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/

Debugging Tools for Windows is a set of tools used to troubleshoot various tasks, they’re more or less intended for driver developers and alike, but can be used for everyday tasks aswell.

Quoted from http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx

• Applications, services, drivers, and the Windows kernel.
• Native 32-bit x86, native Intel Itanium, and native x64 platforms.
• Microsoft Windows NT 4.0, Windows 2000, Windows XP, Microsoft Windows Server 2003, Windows Vista and Windows Server 2008.
• User-mode programs and kernel-mode programs.
• Live targets and dump files.
• Local and remote targets.


Debugging Tools for Windows is a part of the Windows SDK and can be downloaded here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

I use Sysinternals Process Explorer quite a bit in my work where these symbols are very handy.
In a particular case I’ve tracked the use of the Nonpaged Kernel Memory, on which you cannot see the Nonpaged Limit if the symbols ain’t correctly loaded.

Process Explorer can be downloaded here: http://technet.microsoft.com/en-us/sysinternals/bb896653

Start Process Explorer and go to Options -> Configure Symbols

For Dbghelp.dll use this path

C:\Program\Debugging Tools for Windows (x86)\dbghelp.dll

And the Symbols path

SRV*c:\program\sysinternals\win32_symbols*http://msdl.microsoft.com/download/symbols


After that, click the graphs in the top right corner and you’ll see the Nonpaged Limit at the bottom, voila.

This is a vanilla install on a Swedish x86 Windows Server 2003.