C# ПІДРУЧНИКИ / c# / MS Press - Msdn Training Programming Net Framework With C#

" Application Deployment Scenarios

*****************************ILLEGAL FOR NON-TRAINER USE******************************

The examples in this section show how to deploy a simple application, an application that uses a shared assembly, and an application that makes use of assembly versioning.

8Module 4: Deployment and Versioning

*****************************ILLEGAL FOR NON-TRAINER USE******************************

This simple executable file prints a single line to the System.Console, a type that is contained in the .NET Framework class library. It does not reference any other libraries and does not itself produce a library.

To see additional information about the application, double-click Manifest. The following window appears.

The preceding illustration shows the manifest, which contains information about the assembly, including the version (not yet set), external libraries, and types within those libraries, which the application uses.

Deployment

Deployment to computers on which the .NET runtime is installed is a simple process. The Hello World application can run directly from a file server. More advanced programs may involve security issues.

In the simple Hello World case, no files are placed on the workstation, no entries are made in the system registry, and, in effect, there is no affect on the client workstation. There is also nothing to clean up because there is nothing to remove on the client workstation.

As you would expect, HelloDemoCS.exe can also be copied to a local volume. In this scenario, you can remove the program by deleting the file, and as before, nothing would remain on the workstation.

Whether you run HelloDemoCS.exe from a file server or copy it to a local volume, running this application will not break another program, and no other application can cause HelloDemoCS.exe to stop functioning.

A Componentized Application

*****************************ILLEGAL FOR NON-TRAINER USE******************************

The Hello World application that is discussed in the preceding topic is completely trivial and hardly representative of even the simplest real-world application. This topic covers compapp, a componentized application, which uses multiple assemblies.

Creating Stringer.dll

The client, Client.exe, calls types that are contained in a component assembly that is named Stringer (Stringer.dll). The source code for the Stringer assembly, is located in Stringer.cs:

using System;

namespace org {

public class Stringer { private string[] StringSet;

public Stringer() {

StringSet = new string[] { "C# String 0",

"C# String 1",

"C# String 2",

"C# String 3"

};

}

public string GetString(int index) {

if ((index < 0) || (index >= StringSet.Length)) { throw new IndexOutOfRangeException();

}

return StringSet[index];

}

public int Count {

get { return StringSet.Length; }

}

}

}

Like HelloDemoCS.exe, Client.exe contains manifest information about itself, the System library, and the types that the application uses. However, the manifest now contains information about the Stringer assembly.

A MSIL disassembler display of the manifest for Client.exe shows the reference to the Stringer assembly, as in the following illustration.

Deployment

Like the simple application, Client.exe can run directly from a file server on any workstation that has the .NET runtime installed. Client.exe and Stringer.dll can also be copied to a local volume. To remove the application, you need only delete the two files.

Specifying a Path for Private Assemblies

*****************************ILLEGAL FOR NON-TRAINER USE******************************

The preceding Client.exe example has one important weakness: both Client.exe and Stringer.dll reside in the same directory. In the real world, an administrator may wish to use a directory structure to manage assemblies. The .NET Framework provides a configuration mechanism that allows administrators to specify a directory from which to load private assemblies.

Locating Stringer.dll and Client.exe in Separate Directories

Using the preceding Client example, all of the source code is the same, but for illustration purposes the build process has been modified so that the component application’s Stringer.dll is built in its own subdirectory named MyStringer.

cd \compapp

csc /target:library /out:MyStringer\Stringer.dll! MyStringer\Stringer.cs

csc /reference:MyStringer\Stringer.dll Client.cs

Using a Configuration File to Locate Assemblies at Run Time

Although the /reference: compile option locates an assembly in a directory when compiling the program, a separate XML-based application configuration file is required at run time to support assemblies that are located in other directories. For client executable files like the examples that are covered in this module, the configuration file resides in the same directory as the executable file. The configuration file has the complete name of the executable file with an additional extension of .config.