1.8 [Enterprise Library] Parallel Operation

Copyright (c) 2007 Dorian Deng. Signature Sharing is not commercially available.
Reprinted please indicate the source: http://blog.csdn.net/doriandeng/archive/2007/09/17/1788826.aspx

Enterprise Library 3.1 can be installed in parallel with earlier versions of Enterprise Library. New applications that can be written for Enterprise Library 3.1ProgramDeploy together with applications written for earlier versions. In addition, you can also choose to port an existing program. At some time, there is only one assembly to the new version.

If you decide to run in parallel, you must deploy different Enterprise Library versions to different directories. In any specified directory, you cannot mix and match the Assembly from different versions. For example, you cannot access application block 3.0 and cache application block 2.0 in the same directory at the same time.

The published project files are used inAssemblyinfo. CSFile to create an assembly with different version information. This allows you to use a version that is strongly named and cannot be added to the global cache for parallel running.

Partial Transplantation

Each assembly in an application can only reference one version of Enterprise Library, but applications with multiple assembly can reference multiple versions, including using Enterprise Library 2.0. One assembly can be moved to the Enterprise Library Used for. NET Framework 3.0, while other assemblies can be left behind independently. This means that the application can be gradually transplanted, one assembly at a time.

Note:

The Enterprise Library configuration console is specific to the same version as it. a dll of that version must be included in its directory. Otherwise, different configuration console versions must be used when different Enterprise Library application versions are configured.

Some porting is supported, but sometimes the implementation is complicated; otherwise, it is not recommended