This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Note

As you may guess, you can copy the XML content generated by the .NET Framework Configuration utility

into a Visual Studio 

App.config

file for further editing. Using this approach, you can certainly decrease your

typing burden by allowing the tool to generate the initial content.

Understanding Shared Assemblies

Now that you understand how to deploy and configure a private assembly, you can begin to exam-

ine the role of a shared assembly. Like a private assembly, a shared assembly is a collection of types

and (optional) resources. The most obvious difference between shared and private assemblies is the

fact that a single copy of a shared assembly can be used by several applications on a single machine.

Consider all the applications created in this text that required you to set a reference to System.

Windows.Forms.dll. If you were to look in the application directory of each of these clients, you

would 

not find a private copy of this .NET assembly. The reason is that System.Windows.Forms.dll

has been deployed as a shared assembly. Clearly, if you need to create a machinewide class library,

this is the way to go.

As suggested in the previous paragraph, a shared assembly is not deployed within the same

directory as the application making use of it. Rather, shared assemblies are installed into the GAC.

C H A P T E R   1 5