Developing XML Web Services and Server Components with Visual C#™ .NET and the .NET Framework, Exam Cram™ 2 (Exam 70-320) By Amit Kalani, Priti Kalani
Table of Contents
Terms you'll need to understand:
Assembly
Binding policy
Delay signing
Global Assembly Cache (GAC)
Merge module
Native compilation
Publisher policy
Strong name
Techniques you'll need to master:
Creating setup programs for installing a Windows service, a serviced component, a .NET Remoting object, and an XML Web service
Registering components and assemblies
Understanding and implementing binding policy
Planning and configuring applications for side-by-side deployments
Assemblies are the smallest units of versioning and deployment in the .NET applications. When a .NET application requests assemblies, the common language runtime (CLR) follows a set of rules called binding policy to locate the assemblies. Binding policy is a deciding factor in how and where an application's assemblies should be deployed.
The .NET Framework greatly simplifies various deployment tasks. In fact, just copying the files on the target computer can easily deploy some simple applications. For advanced deployment options and requirements, however, you might want to create a Windows Installer based setup project.
