parts of .net assembly

Smart Lucky

14y5.8kVisual Basic .NET

hi can any one tell me exactly how many parts of .net assembly ...?

5 Replies

Know the answer? Post it — somebody with the same question will find it here.

Senthilkumar14y ago
Hi ,

An assembly is a partially compiled code library. In .NET, an assembly is a portable executable and can be an EXE (process assembly) or a DLL (library assembly). An assembly can consist of one or more files or modules in various languages. It is used in deployment, versioning and security

http://visualbasic.about.com/od/FWTools/a/FWAssemblies.htm
0
Vulpes14y ago
Sometimes the 'assembly manifest' is simply called 'the manifest' as it's mandatory for an assembly to have one.

It contains the assembly's name, version, culture, strong name (if applicable), a list of the files it comprises and details of other assemblies which it references.

However, there is also something called an 'application manifest'. This is an XML file which is normally embedded in the assembly as a resource and contains (amongst other things) deployment details.
0
Smart Lucky14y ago
hi
dear ok but what is difference b/w Manifest and an Assembly Manifest
0
MuthuMari M14y ago
Hi,

An assembly is a partially compiled code library. In .NET, an assembly is a portable executable and can be an EXE (process assembly) or a DLL (library assembly). An assembly can consist of one or more files or modules in various languages. It is used in deployment, versioning and security.

thanks.

If this post is useful then mark it as "Accepted Answer"
0
Vulpes14y ago
There are 4 parts, namely:

1. The assembly manifest, which contains metadata for the assembly itself.

2. Type metadata for the types used in the assembly.

3 Intermediate language (IL) that implements the types.

4. Resources used.

These parts may not necessarily be in a single physical file but can be spread over several files.
0