URL Rewrite 2.0 Performance

Do performance work it is easy when you have the right tools for measuring gains or lost. I will share some thoughts about how to improve performance during rewriting, but please keep in mind that any change you do must be well thought and with performance numbers in hand. If you need advice, please use…

1

Getting the line number for a Faulting Application Error

It is possible to know the line where an application faulted even if it was not running under debugger or memory dump is not available. It won’t probably tell you why it failed, but it will give you at least a point where to start investigating. After the application failed, look at the Windows Event…

0

Enable code coverage in Visual Studio

For some reason, every time that I want to enable code coverage for a library that I’m unit testing, I found hard to remember how to enable this fabulous feature. Here are the steps (that work for me): Double click the [Local].testsettings file in the Solutions Items folder in the Solution Explorer window. In the…

4

Registry values for IIS URL Rewrite

The following registry values can be set for the IIS URL Rewrite module and will affect the global behavior of the module; use them at your own risk All these values (DWORD) can be set under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\Rewrite MaxBackReferences – By default 31 (maximum value). Defines the maximum number of back-references that can…

0