This post originated from an RSS feed registered with .NET Buzz
by Anand M.
Original Post: NProf in Windows 2003
Feed Title: .NET From India
Feed URL: http://www.dotnetindia.com/index.rss
Feed Description: Your daily dose of .NET From India
I have been playing around with different tools to look at ASP.NET application performance including CLR Profiler and NProf. NProf has not been updated for a long time and is still in Alpha, but if you want a free profiler , then it is one you can have a look at.
There is a problem with it running on ASP.NET applications on Windows 2003. When you are using it with an ASP.NET application, it hooks into IIS6 and does the profiling. But it is unable to actually stop profiling. So instead of using the Stop Profiling option, just go to command line and do an iisreset. It is able to detect this and automatically stop profiling. Then you can go and start looking at the results. I also found that it does not seem to unhook cleanly and that even if I am not profiling, the IIS response seems to be slow. So I had to do an iisreset and then uninstall NProf before IIS was back to normal. I am not sure if this was a one off thing, but I also found this problem occur on another Win 2003 machines. So I assume it is a problem with NProf working with Win 2003.
Previous Topic
