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

Lab 4: Packaging and Deployment

Topic Objective

To introduce the lab.

Lead-in

In this lab, you will build an application that is named client, which retrieves an array of strings from an instance of the Stringer class and reverses the order of these strings by using an instance of the AReverser class. These classes are packaged in two separate assembly libraries that are named Stringer.dll and AReverser.dll.

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

Objectives

After completing this lab, you will be able to:

!Create an application by using private assemblies in multiple directories.

!Install and remove a strong-named assembly from the global assembly cache.

!Configure an application to control its binding to an assembly based on the assembly’s location and version data.

Lab Setup

Starter and solution files are associated with this lab. The starter files are in the folder <install folder>\Labs\Lab04\Starter. The solution files are in the folder <install folder>\Labs\Lab04\Solution.

Scenario

You will build an application that is named client, which retrieves an array of strings from an instance of the Stringer class and reverses the order of these strings by using an instance of the AReverser class. These classes are packaged in two separate assembly libraries that are named Stringer.dll and AReverser.dll.

Estimated time to complete this lab: 50 minutes

Exercise 1

Locating Private Assemblies in Multiple Directories

In this exercise, you will build the client application by using private assemblies that are located in multiple directories.

!Examine the application

•Open Notepad and examine the source code for the files that are listed in the following table.

! Compile and build the application in a command window

Important To use Microsoft Visual Studio .NET tools within a command prompt window, the command prompt window must have the proper environment settings. The Visual Studio .NET Command Prompt window provides such an environment. To run a Visual Studio .NET Command Prompt window, click Start, All Programs, Microsoft Visual Studio .NET,

Visual Studio .NET Tools, and Visual Studio .NET Command Prompt.

1.Go to the MyStringer directory and build the private assembly library named Stringer.dll in that directory.

2.Go to the AReverser directory and make the private assembly named AReverser.dll in that directory.

3.Go to the Compapp directory and build the client application, referencing the private assemblies from steps 1 and 2. Reference the DLLs in their own directories. Do not copy them to the Compapp directory.

! Execute the application

1.Run the Assembly Binding Log Viewer by executing Fuslogvw.exe. Click on the right hand check box labeled Log Failures.

2.Execute the Client.exe application and note the exception in the space that is provided.

3.In the Assembly Binding Log Viewer click on Refresh. Then double click on the Client.exe application, and view the log entry.

4.Create a configuration file in the Client directory to specify the appropriate privatePath so that the application can successfully bind and load the necessary classes.

The Client.exe application should generate the following output:

Strings from StringComponent

C# String 0

C# String 1

C# String 2

C# String 3

Reversed Array Strings

C# String 3

C# String 2

C# String 1

C# String 0

! Compile, build, and execute the application

1.From a command prompt window, navigate to the Client directory and build the client application. Reference the private assembly MyStringer\Stringer.dll and the strong-named assembly AReverser_v2.0.0.0\AReverser.dll.

2.Execute the Client.exe application, which should generate the following output:

Strings from StringComponent

C# String 0

C# String 1

C# String 2

C# String 3

Reversed Array Strings

C# String 3

C# String 2

C# String 1

C# String 0

! Configure to bind to the latest version of AReverser

Tip You can obtain the publicKeyToken tag’s value by examining the global assembly cache using gacutil /l or the cache shell extension.

1.Modify the configuration file to bind to the incompatible later version 2.0.1.0 of AReverser.

2.Execute Client.exe and note the exception.

3.Use the global assembly cache tool to remove the two strong-named versions of AReverser.

4.Confirm the removal of the two strong-named versions of AReverser by viewing the global assembly cache with Gacutil.exe and Windows Explorer.

4.Describe how an application can use an assembly that is located in an application’s subdirectory.

Create a configuration file in the application’s directory that specifies a PrivatePath as follows:

<configuration>

<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="MyStringer"/>

</assemblyBinding>

</runtime>

</configuration>

5.What kind of assembly can be placed in the global assembly cache and be versioned?

A strong-named assembly.

6.What command is used to generate public-private key pairs?

The Strong Name (Sn.exe) tool is used to generate a new key pair and place them in a file:

sn –k orgKey.snk

7.What command is used to install a strong-named assembly into the global assembly cache?

> gacutil -i <filename>

Module 5: Common

Type System

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

2001-2002 Microsoft Corporation. All rights reserved.

Microsoft, ActiveX, BizTalk, IntelliMirror, Jscript, MSDN, MS-DOS, MSN, PowerPoint, Visual Basic, Visual C++, Visual C#, Visual Studio, Win32, Windows, Windows Media, and

Window NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.