![]() If the value is TRUE and “Developer Command Prompt for VS2013” is used instead of “VS2013 圆4 Native Tools Command Prompt”, we will get an error during step when we attach the w3wp.exe process using “vsperfcmd /ATTACH:w3wp.exe” Use the “VS2013 圆4 Native Tools Command Prompt” instead of “Developer Command Prompt for VS2013” to execute all the steps mentioned in the blog. Step 2: If the application is 32 bit and if Enable 32-Bit Application property is set to TRUE: run-> INETMGR -> The relevant application pool -> Advanced Settings -> Enable 32-Bit Applications This behaviour is configured using the property “Enable 32-Bit Applications”. On a 64 bit machine the configurations are such that even a 32-bit application can run in the 64 bit environment. Step1 : Very Important : Check application pool’s Version (64 bit / 32 bit) support: ![]() These are few more points to be noted while setting up the code coverage environment especially for IIS based applications (IIS 7.0 and above) on a 64-bit server machine: If any step is missed/ignored and if the sequence is changed the code coverage is not going to work. Your blog post on code coverage has helped me in setting up a code coverage environment in the project on which I am working.įor other readers of this blog spot, every step mentioned in the post have to be executed exactly in the same way and in the same sequence. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |