http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I've tried this before and ended up with all sorts of problems with PerfMon and IIS so be very careful with it! http://ayende.com/2129/coverage-during-acceptance-tests#comment2http://ayende.com/2129/coverage-during-acceptance-tests#comment2Fri, 23 Feb 2007 01:24:35 GMTHi, Following a section from the NCoverFAQ.html distributed with the 1.3 version. Haven't tried this myself but it might help you. --> Start snippet 7. How do I analyze an ASP.NET application with NCover? xmspc got this to work on ASP.NET. See his post on the message board for more information. Here are the basics for getting it to work on Windows XP. 1) Ensure the NCoverLib COM component is registered (setup does this, but you can manually register it with regsvr32 if you wish). 2) Set the machine-wide COR profiling environment variables (or find some other way to get them set in the aspnet_wp.exe's environment): COR_ENABLE_PROFILING=1 COR_PROFILER=CvrLib.CoverageProfiler 3) Create %windir%\System32\Coverage.log and %windir%\System32\Coverage.xml and grant .\ASPNET read+write+modify permission to these 2 files only. 4) Force a restart of IIS so aspnet_wp.exe picks up the new environment variables. Coverage info will be written to the System32 directory. All ASP.Net processes (on Windows XP for sure, don't know about Windows 2003) use %windir%\System32 as their working dir, therefore if multiple processes are running they will stomp over the Coverage files. ...would be nice if NCover used AppDomain basedir and/or value from app config file to set output file dir... <-- End snippet http://ayende.com/2129/coverage-during-acceptance-tests#comment1http://ayende.com/2129/coverage-during-acceptance-tests#comment1Thu, 22 Feb 2007 22:32:51 GMT