This post originated from an RSS feed registered with .NET Buzz
by Raymond Lewallen.
Original Post: What's in your manifest file?
Feed Title: Raymond Lewallen
Feed URL: /error.htm?aspxerrorpath=/blogs/raymond.lewallen/rss.aspx
Feed Description: Patterns and Practices, OOP, .Net and Sql
The manifest is the heart and soul of managed code. The
manifest contains all the metadata that describes an assembly and its
modules. Manifest files can be very complex, but all have the
basic, similar components. The following is the information
contained in the manifest file.
Contents â contains information about the external types and resources exposed by the assembly in two metadata tables: ExportedType and ManifestResource.
Custom attributes â contained in the CustomAttribute metadata table, this has information that compilers use.
Dependencies â contained in three metadata tables: AssemblyRef, File and ModuleRef
Assemblies referenced by this assembly
Modules contained within this assembly
Identity â contains the following information about the assembly in two metadata tables: Module and Assembly
Name
Version number
Culture (optional) if the assembly contains localized resources
Language
Processor architecture
Public key (optional) if the assembly is strongly named
Type
Requested permissions â contains information about
the permissions for the assembly. If specific permissions exist
for classes and methods within the assembly, this information is also
contained here, in the metadata table DeclSecurity.
Here is the xml manifest file from NDocGui:
XML Manifest File<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" language="*" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" /> </dependentAssembly> </dependency> </assembly>
And here is a partial xml manifest file from Sql Server 2005 Report Builder: