By definition, satellite assemblies only contain resource files.
按照定义，附属程序集只包含资源文件。
Satellite assemblies will be created along with the main assembly.
附属组件可以与主要组件一起建立。
You can deploy your application's resources in satellite assemblies.
您可以在附属组件中部署您应用程序的资源。
Satellite assemblies are often used to deploy language-specific resources for an application.
附属程序集常用来为应用程序部署一种语言所特有的资源。
The . NET Framework provides support for versioning the main assembly and satellite assemblies.
出版商策略程序集提供对附属程序集的版本控制支持。
You can update and change an application's satellite assemblies without recompiling the application.
您无需重新编译应用程序，即可更新和更改应用程序的附属程序集。
This requires resources to be either compiled into satellite assemblies, or a part of the application's main assembly.
这需要编译资源成附属组件，或者应用程序主要组件的一部分。
An application needs to load only those satellite assemblies that contain the resources needed for a particular culture.
应用程序只需加载那些包含特定区域性所需的资源的附属程序集。
The common language runtime provides support for retrieving culture-specific resources that are packaged and deployed in satellite assemblies.
公共语言运行时为检索打包和部署在附属程序集中的区域性特定资源提供了支持。
A drawback of this approach is that it downloads all satellite assemblies whenever the application is installed or updated on a client computer.
这种方法的缺点是不管应用程序要在用户端电脑上安装或更新，都会下载所有的附属组件。
In the satellite assembly deployment model, you create an application with a default assembly (the main assembly) and several satellite assemblies.
在附属组件部署模型中，您以一个预设组件(主要组件)和数个附属组件来建立应用程序。
In the satellite assembly deployment model, you create an application with one default assembly (which is the main assembly) and several satellite assemblies.
在附属程序集部署模型中，您所创建的应用程序具有一个默认程序集(作为主程序集)和几个附属程序集。
The fallback resource file is built into the main assembly, and the culture-specific resource files are then built into satellite assemblies, one for each UI culture.
回溯资源档内建于主要组件中，接著特定文化特性的资源档则会内建到附属组件中，每个UI文化特性都各有一个资源档。
However, you might not want to ship new copies of your satellite assemblies if the existing ones are sufficient and compatible with the newer version of your product.
但是，如果现有附属程序集已足够并且与产品的新版本兼容，则通常无需提供附属程序集的新副本。
Fortunately, Visual Studio knows how to name the satellite assemblies correctly and how to deploy them in the correct directory structure expected by the.net assembly loader.
幸运的是，VisualStudio知道如何正确命名附属程序集，以及如何在. NET程序集加载器所期望的正确目录结构中部署它们。
Because the satellite assemblies are not part of the main assembly, you can easily replace or update resources corresponding to a specific culture without replacing the application's main assembly.
因为附属程序集不是主程序集的一部分，所以您不必替换该应用程序的主程序集，即可很容易地替换或更新与特定区域性相关的资源。
If you want to deploy strong-named assemblies in the application directory, you will not be able to increment a satellite assembly's version number when you update the assembly.
如果要在应用程序目录中部署带强名称的程序集，则将不能在更新程序集时递增附属程序集的版本号。
If you want to deploy strong-named assemblies in the application directory, you will not be able to increment a satellite assembly's version number when you update the assembly.
如果要在应用程序目录中部署带强名称的程序集，则将不能在更新程序集时递增附属程序集的版本号。
应用推荐