Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are developing a system using c# in Visual Studio 2008.
When I configure VS to instrument my dll’s and run the tests, only the dll that is not signed gets instrumented (nice way to find that we forgot one).
Is there a way to generate code coverage on signed dll’s or do I have to un sign them, run the analysis and then sign them again?
Thanks
Shiraz
The reason you can not instrument a signed assembly is that the instrumentation process changes the contents of the assembly. This would change the hash of the assembly hence invalidating the digital signature.
The best approach is to unsign the assembly for the profiling run.