如何使用SN.EXE -Vr [英] how to use sn.exe -Vr

查看:687
本文介绍了如何使用SN.EXE -Vr的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

从MSDN的帮助下,它说的-Vr选项是:

From the MSDN help, it says the -Vr option is:

注册组件验证跳跃。

Registers assembly for verification skipping.

我的问题是,当-Vr时,将只更改程序集文件本身或者它会修改系统注册表以及。这一点很重要,我是否应该在开发机器或在最终部署的机器发出此命令。

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创建本地计算机上的注册表中的项。它不修改程序集。您必须运行SN -vr在本地您要跳过验证目标集的强名称的每一台机器上。

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.

既然你提到,你关心的是测试机,你可能要记住,至少有一些您的测试运行,真的应该对为已装船应用程序的状态,这将包括运行最后签名的程序集。虽然我明白,关键管理问题可能preclude申请的最后签名,说,自动生成,你最终将需要测试使用完全签名的程序集,并没有验证跳过,如果你想模仿的最终执行环境。

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.

这篇关于如何使用SN.EXE -Vr的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆