Microsoft BizTalk Server 2004: Creating Schemas - Exercise 6 Assigning a Strong Name to the Assemblies

(Page 7 of 7 )

 

Scenario

In this exercise, you will create and assign a strong name for the BizTalk assemblies you are about to build. A strong-named assembly provides several security benefits. A strong name guarantees the uniqueness of the assembly by assigning a digital signature and a unique key pair. This also protects the lineage of the assembly by ensuring that no one else can generate a subsequent version of that assembly. And finally, a strong name provides a strong integrity check to guarantee that the contents of the assembly have not been changed since it was built.

        Tasks              Detailed steps

1. Create a strong name assembly key file.
   
   This creates a strong name public/private key pair, which is saved to an assembly key file.
   
   
   1. Click Start | Programs | Microsoft Visual Studio .NET 2003 | Visual Studio .NET Tools | Visual Studio .NET 2003 Command Prompt.
      
      The Visual Studio .NET command prompt appears. 
      
      
   2. At the command prompt, type cd C:\Labs\Work and then press ENTER. 
      
   3. Type sn -k Key.snk and then press ENTER.
      
      A message appears, indicating that the key pair has been written to the key file (Key.snk). 
      
   4. Type Exit to close the Command Prompt.
      
2. Assign a strong name to the assembly.
   
   This assigns the key file to the assembly. You must do this for each of the projects in this solution.
   
   
   1. In Solution Explorer, right-click the NWMessaging project, and then select Properties. 
      
   2. In the left pane of the NWMessaging Property Pages page, click Assembly.
      
   3. In the right pane, scroll down to the Strong name section, click the field to the right of Assembly Key File, and then click the ellipsis (…) button. 
      
   4. In the Assembly Key File dialog box, navigate to C:\Labs\Work\Key.snk, and then click Open.
       
      
      
      
   5. Click OK to save changes.

Exercise 7 Building the Schema Project

Scenario

In this exercise, you will build the project to generate an assembly that contains the resources (the schemas) that you have just created. This also ensures that that there are no compile-time errors in the work you have completed so far.

        Tasks              Detailed steps

1. Build the project.
   
   The assembly is compiled into a DLL file and saved in the …\bin\Development folder within the project folder.
   
   
   1. On the File menu, click Save All.
      
   2. In Solution Explorer, right-click NWMessaging, and then select Build.
      
      The results of the compiled schema project are displayed in the output window. Do not deploy this assembly, because deployment could affect later labs. 
      
   3. Close Visual Studio.

Take Microsoft software for a test drive. With MSDN Virtual Labs, you get full access to all available Microsoft products through 90-minute modules, each with its own downloadable manual. Try this lab out now.

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

Comments On: Microsoft BizTalk Server 2004: Creating Schemas

· We hope you found this article from MSDN Virtual Labs to be enjoyable and...   >>> Post your comment now!