Merge modules . msm files allow you to share components between multiple deployment projects 合并模块( . msm文件)使您得以在多个部署项目之间共享组件。
Knowing what roots depend on a shared component assembly is useful in gauging the impact of an 了解哪些根依赖于共享组件程序集对于在共享组件升级后确定
If you have shared components that are strong - named , place them in the global assembly cache 如果您有强命名的共享组件,则请将它们放置在全局程序集缓存中。
As you might imagine , examining all of the system boundaries and shared components is a difficult task 可以想像,检查所有的系统边界和共享组件这一任务很困难。
Changing the installation path for one shared component also changes it for the other shared components 更改一个共享组件的安装路径会同时更改其他共享组件的安装路径。
Demonstrates how to use merge modules . msm files to share components between multiple deployment projects 演示如何使用合并模块( . msm文件)在多个部署项目之间共享组件。
To defer native image generation when installing a new application or when updating a shared component , use the 若要在安装新的应用程序或更新共享组件时推迟本机映像的生成,请将
How to use merge modules to ensure that shared components are packaged and delivered for consistent deployment 演示如何合并模块,确保将共享组件一起打包和分发,从而实现一致的部署。
Similarly , changes to a shared component or changes to computer settings might require many native images to be updated 同样,更改共享组件或更改计算机设置可能需要更新很多本机映像。
Publisher policy files are distributed by a component publisher as a fix or update to a shared component 发行者策略文件是由组件发行者作为共享组件的修正或更新( qfe或service pack )分发的。