The Global Assembly Cache in the .NET Framework provides a central place for registering
assemblies. Registered assemblies are then available to all applications, including
the development environments like Visual Studio.NET and Web Matrix.The process of
adding an assembly to the Global Assembly Cache can be compared to the process of
registering COM components in the server, as is done in the case of Windows DNA
applications.The first step involved in adding an assembly is to strong-name the assembly. A strong
name is basically assigned to an assembly or a component to distinguish it from other
assemblies and components existing in the GAC. A strong name consists of an assembly
identity (name, version, and so on), a public key, and a digital signature.Assigning a strong name to an assembly ensures that it is unique, has version protection,
and has code integrity. Assigning a strong name to an assembly is not a difficult task.
You can use the sn.exe utility to generate strong names, which are then added to the
code of the assembly. For example, to create a strong name for an assembly named sample.
dll, you would write the following in the command prompt:
c:\MyAssembly>sn -k sample.snk
This would generate a strong name keypair and store it in a file named sample.snk.The
file extension can be anything, but.SNK is normally used as a convention.The -k option
creates a strong name keypair.There are other options that you can search for in MSDN.
The second step is to associate the generated strong name file with the assembly.Add
the following code to your assembly to associate the strong name. By default,Visual
Studio .NET projects include skeleton declarations of these attributes in the AssemblyInfo file.
Imports System.Reflection
<assembly: AssemblyKeyFile(“sample.snk”)>
Note here that the information regarding the file containing the strong name keypair is
placed in the code file before any namespace declaration. Also, you must import the
System.Reflection namespace in order for the statement to work, otherwise the compiler
will not recognize the <assembly: AssemblyKeyFile(“sample.snk”)> statement.
After compiling the assembly with the statements containing the strong name information
being added to it, you now have to place the assembly into the GAC.You can do
this manually by simply copying and pasting the assembly into the GAC, which is located
at C:\WINNT\ASSEMBLY\.
You can also use the gacutil.exe utility, installed with the .NET Framework. In order
to add an assembly, you write the following on the command prompt:
gacutil /i sample.dll
The /i option is for installation. In order to remove an assembly from the GAC, you can
use the same utility, as follows:
gacutil /u sample.dll
The /u option is for uninstalling or removing an assembly from the cache.Typing
gacutil /? lists all of its options.
Subscribe to:
Post Comments (Atom)
Archives
-
▼
2008
(100)
-
▼
September
(72)
- You can stream the binary data returned by SQL Ser...
- Inserting an Image into SQL Server
- Executing a Stored Procedure with No Results Returned
- Using a Tool to Create a Data Access Layer
- Using Microsoft’s Data Access Application
- Connecting to an ODBC Datasource
- Connecting to MySQL Database
- Connecting to a Microsoft Access Database
- Connecting to Oracle
- Connecting to SQL Server
- Catching Exceptions
- Handling Page Level Errors
- Raising Exceptions
- Enabling Page Level Tracing
- Logging Error Details
- Configuring a Default Error Page in ASP.NET
- Perform Custom Authentication on Each Request
- Creating a Simple Forms Authentication Logout Page
- Creating a Simple Forms Authentication Login Page
- Requiring Authentication to Access Files and Folders
- Configuring Windows Authentication
- Configuring Forms Authentication
- Reading and Storing Data in ViewState
- Reading and Storing Data in Cookies
- Reading and Writing Values to the Session Object
- Reading and Writing Values to the Application Object
- Configuring Sessions in your ASP.NET Application
- Configuring Application Error Handling
- Configuring Application Debugging
- Configuring Application Tracing
- Creating Custom Application Settings in the web.co...
- Storing and Reading Custom Settings from the web.c...
- Customizing Output for a Device
- Displaying ObjectList Information in a Table
- Configuring Automatic Paging of Content
- Navigation in a Mobile Web Form
- Creating a Mobile Web Form
- Implementing a CallBack when a Cached
- Using HttpContext for Per-Request Caching
- Varying Output Caching by HTTP Headers
- Varying Output Caching by Browser
- Varying Output Caching by Parameter(s)
- Creating a Cache Dependency
- Retrieving Data from the Cache
- Inserting Data into the Cache
- Partial Page Output Caching Using VaryByControl
- Page Output Caching
- Installing a Component in the Global Assembly Cach...
- Data-binding a TreeView Control
- Using the ToolBar IE Web Control
- Using the TabControl and PageView IE Web Controls
- Dynamically Adding Controls to a Web Form
- Creating a Templated Control
- Creating a Data-bound Control
- Creating a Composite Control
- Creating ViewState-Enabled Control Properties
- Extending Existing Web Controls
- Declaring a Simple Custom Control
- Programmatically Accessing Properties of a Late-Bo...
- Sharing User Controls Across Application Domains
- Raising Events from a User Control
- Dynamically Adding User Controls to a Web Form
- Partial Page Output Caching in ASP.NET
- Dynamically Adding User Controls to a Web Form in ...
- Getting and Setting User Control Properties in ASP...
- Adding a User Control to a Web Form in ASP.NET
- Declaring a User Control in ASP.NET
- Adding Client-Side Script to a Web Form in ASP.NET
- Persisting Data on a Web Form between Postbacks in...
- Working with ListBoxes in ASP.NET
- Creating Dependent DropDownList Controls in ASP.NET
- Working With DropDownLists in ASP.NET
-
▼
September
(72)
No comments:
Post a Comment