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.
From the MSDN help, it says the -Vr option is:
Registers assembly for verification skipping.
My question is when the -Vr is used, will it only change the assembly file itself or it will change the system registry as well. This matters whether I should issue this command in the development machine or in the final deployed machine.
sn -Vr creates an entry in the registry on the local machine. It does not modify the assembly. You must run sn -Vr locally on every machine on which you wish to skip verification of the target assembly’s strong name.
Since you mention that your concern is for a test machine, you may want to keep in mind that at least some of your test runs really ought to be run against the “as shipped” state of the application, which would include the final signature for assemblies. While I understand that key management concerns might preclude applying the final signature to, say, automated builds, you’re eventually going to need to test using fully signed assemblies and no verification skipping if you want to emulate the eventual execution environment.