In Dot Net, Assemblies are regarded as the Building Blocks. There are a wide number of reasons for regarding the assemblies as the Building Blocks. Some of them are the following:

Assemblies: The Building Blocks

Assemblies are the building blocks used by the.NET Framework to resolve the versioning and deployment matters just described. Assemblies are the deployment units which are basically meant for types and resources. In a wide number of ways an assembly equates to a DLL in today's world; as a response, assemblies are a "logical DLLs."

What is Metadata and what are the Usages?

Assemblies are self-descriptive through metadata called a manifest. Just as.NET uses metadata to portray types, it also uses metadata to illustrate the assemblies that contain the types.
Assemblies are definitely something more than mere deployment. For example, versioning in.NET is done at the assembly level-nothing lesser, much similar to a module or a type, is versioned. Also, assemblies are extremely useful for sharing code between applications. The assembly that a type is contained in is an integral part of the characteristics of the type.

The code access security system makes use of assemblies at the core of its permissions model. The author of an assembly makes a recording of the manifest the set of permissions needed to run the code, and the administrator grants permissions to code rooted in the assembly in which the code is contained.

Finally, assemblies are also regarded as an integral part of the type system and the run-time system in that they set up a visibility boundary for types and serve as a run-time extent for resolving references to types.

Assembly Manifests

Specifically, a manifest comprises the following data about the assembly:

* Identity. An assembly's identity comprises four parts: a simple text name, a version number, an elective culture, and an optional public key if the assembly was constructed for sharing.

* File list. A manifest consists of a list of all files that make up the assembly. For each file, the manifest makes a recording of its name and a cryptographic hash of its contents at the time the manifest was constructed. This hash is confirmed at run time to make sure that the deployment unit is consistent.

* Referenced assemblies. Dependencies between assemblies can be maintained in the calling assembly's manifest. The dependency information consists of a version number, which is used at run time to guarantee that the correct version of the dependency is loaded.

* Exported types and resources. The visibility options which can be accessed to types and resources include "visible only within my assembly" and "visible to callers outside my assembly."
Dot Net Programmer [http://www.akrostechnology.com/] needs to know all these factors and keep them in mind for enhancing the overall application development process.