Microsoft Windows NT 4.0 Guide Manual do Utilizador descarregar pdf (Página 140)

Microsoft

Windows Server

™

2003 White Paper

Windows NT 4.0 Server Upgrade Guide 135

types contained in a DLL were the same types that the application was built with. As a result, a

new version of a component could overwrite an older version and break applications.

Side-by-side execution and the .NET Framework provide the following features to eliminate DLL

conflicts:

• Strong-named assemblies. Side-by-side execution uses strong-named assemblies to bind type

information to a specific version of an assembly. This functionality prevents an application or

component from binding to a version of an assembly that is not valid. Strong-named assemblies

also allow multiple versions of a file to exist on the same computer and to be used by applications.

• Version-aware code storage. The .NET Framework provides version-aware code storage in the

global assembly cache, a computer-wide code cache present on all computers on which the .NET

Framework is installed. The global assembly cache stores assemblies based on version, culture,

and publisher information, and supports multiple versions of components and applications.

• Isolation. Using the .NET Framework, you can create applications and components that execute

in isolation, an essential component of side-by-side execution. Isolation involves being aware of

the resources you are using and taking care when sharing resources among multiple versions of

an application or component. Isolation also includes storing files in a version-specific way. For

more information about isolation, see “Guidelines for Creating Applications and Components for

Side-by-Side Execution” in the .NET Framework Software Development Kit Help.

1 2 ... 135 136 137 138 139 140 141 142 143 144 145 ... 154 155

Sem comentários

Microsoft Windows NT 4.0 Guide Manual do Utilizador Página 140