PREFINALS | .NET Assemblies | Event-Driven Programming

Assemblies

These are files that contain compiled code targeted at the .NET Framework. These are basically physical packages meant for distributing code. The .NET classes are actually contained in several assemblies (Harwani, 2015, p. 621).

Metadata, Manifest

An assembly has two (2) sections:

Metadata

It includes information about the data types of the program that are being used.

Manifest

It holds the information of the assembly, which consists of the name, version number, and the type of mapping information.

.exe, .dll

An assembly also has two (2) file extensions:

.exe

for standalone applications

.dll

for reusable components.

C:\Windows\assembly

.NET Frameworks’ core assemblies location can be found in.

Private Assembly

Simplest type of assembly.

Private Assembly

Can only be used within a software package that is intended to be used.

Private Assembly

Two (2) private assemblies with the same class name are not a problem since the application can only see the classes that are mentioned in its private assemblies Private Assembly

Shared Assemblies

These are libraries that other applications can commonly use. Security precautions are necessary when using a shared assembly since any other software can access a shared assembly.

Name Collision

It is a common problem in shared assembly wherein other classes or variables have the same name that matches with the other shared assembly.

Name Collision

A different form of the same assembly might overwrite the shared assembly, and the new version might be incompatible with the existing code.

Name Collision

Shared assemblies are given a strong, unique name based on the private key cryptography to avoid name collision.

Global Assembly Cache (GAC)

It enables several applications to share shared assembly.

Global Assembly Cache (GAC)

It is required to add the assembly to the special directory.

Global Assembly Cache (GAC)

It is a centralized storage location for .NET Assemblies.

Step 1

Which step of Creating a Shared Assembly is this:

Create a project containing a class file. The class file contains the methods and properties that you want other applications to access.

Step 2

Which step of Creating a Shared Assembly is this:

Generate a strong name for the project. The strong name is saved in a strong key filename (e.g., ShareAssemblyMessageKeyFile). The strong key file is created named ShareAssemblyMessageKeyFile.snk and located at the solutions explorer.

Step 3

Which step of Creating a Shared Assembly is this:

Specify the key filename in the project by indicating its strong key filename in the AssemblyInfo.cs file.

Step 4

Which step of Creating a Shared Assembly is this:

Compile the project to generate an assembly. The assembly is generated with the extension .dll.

methods and properties

Create a project containing a class file. The class file contains the __ ____ _that you want other applications to access.

strong key filename

Generate a strong name for the project. The strong name is saved in a _ _ (e.g., ShareAssemblyMessageKeyFile). The strong key file is created named ShareAssemblyMessageKeyFile.snk and located at the solutions explorer.

AssemblyInfo.cs

Specify the key filename in the project by indicating its strong key filename in the _ file.

.dll

Compile the project to generate an assembly. The assembly is generated with the extension ____.