Manifest and Assemblies in dotnet framework

Assembly: A compiled code library used for deployment, versioning, and reuse (e.g., .dll or .exe file).

Manifest: A part of the assembly that contains metadata like assembly name, version, culture, and referenced assemblies.

Suppose you have a class library project:

public class MyMath
{
    public int Add(int a, int b) => a + b;
}

When you build it, you get MyLibrary.dll → This is the assembly.

Inside MyLibrary.dll, the manifest contains:

• Assembly name: MyLibrary
• Version: 1.0.0.0
• List of dependencies
• Culture info

Think of assembly as the full package, and the manifest as the label that tells what's inside.

Good Luck!

Assembly in .NET:
An assembly is the basic unit of deployment and versioning in .NET. It is a compiled code library used by applications for execution.

• Types of Assemblies:
  • Executable Assembly (.exe) – Runs as a standalone application.
  • Library Assembly (.dll) – Used as a shared library by other assemblies.
• Key Features:
  • Contains compiled IL (Intermediate Language) code.
  • Stores metadata about types, references, etc.
  • May include resources (images, strings, etc.).
  • Enforces versioning and security boundaries.

Manifest in .NET:
The manifest is a part of the assembly that contains metadata about the assembly itself. It Contains assembly name, version number, culture information, list of files, referenced assemblies.
The manifest ensures that the .NET runtime knows:

• What types and resources the assembly contains
• What other assemblies it depends on
• How to bind to the correct version