Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
- Bellevue .NET User Group
- This group is an initiative from "Vidya Vrat Agarwal" a .NET Passionate. This group is created with a vision to encourage and help people learn Microsoft .NET technology. This group also provides a platform to share ideas, thoughts and experiences an individual may have while learning and implementing .NET technologies.
Search This Blog
Events / Announcements
Group Presentations Slides / Resources
Articles
- Understanding Bug Triage– Severity & Priority
- What is a Service?
- What is a Web Service?
- Purpose of Metadata
- CLS Compliance - Problem Scenario & Solution
- Chart your Career
- Abstraction and Encapsulation Defined
- Finalizer in .NET
- What .NET is all about
- Code Names
- Father of C#
- Journey through .NET 1.0 to .NET 3.5
- VS 2008 - A solution to long lived coupling between Visual Studio and .NET Framework
Questions & Answers
- Two Main() function in an application?
- What is Managed code?
- What is Metadata and Manifest?
- What is the difference between an Assembly and a Namespace?
- What is versioning? Can Versioning be applied to Private assemblies?
- What is an Exception, how do you achieve Exception Handling in .NET?
- What are the access modifiers C# supports and their purpose?
- What is the difference between Abstract class and an Interface?
- How do you achieve multiple inheritance in .NET?
- What is the advantage of "sealed" keyword in real-world of software development?
- What are the features Inheritance offer above an object creation?
- Would you write your own finalizer/destructor of let .NET GC do the cleanup?
- What is the difference between loading behavior of an .exe and .dll ?
- Why would you choose an .exe over a .dll ?
- Difference between .NET Assembly and a .dll /.exe
Blog Archive
-
▼
2010
(34)
-
▼
April
(21)
- Chart your Career
- What is an Exception, how do you achieve Exception...
- What is versioning? Can Versioning be applied to P...
- What is Metadata and Manifest?
- What is Managed code?
- What is the difference between an Assembly and a N...
- Abstraction and Encapsulation Defined
- Finalizer in .NET
- What are the access modifiers C# supports and thei...
- What is the difference between Abstract class and ...
- How do you achieve multiple inheritance in .NET?
- What is the advantage of "sealed" keyword in real-...
- What are the features Inheritance offer above an o...
- Would you write your own finalizer/destructor or l...
- Limitations of GAC deployed assembly
- How to use a GAC deployed assembly in an application
- Steps to deply an assembly in the GAC
- What is the difference between loading behavior of...
- Why would you choose an .exe over a .dll ?
- Difference between .NET assembly and a .dll/.exe
- Talk on .NET assemblies
-
▼
April
(21)
1 comment:
Metadata :-
Metadata is binary information describing the program that is stored either in a common language runtime portable executable (PE) file or in memory. When you compile your code into a PE file, metadata is inserted into one portion of the file, while the code is converted to Microsoft intermediate language (MSIL) and inserted into another portion of the file. Every type and member defined and referenced in a module or assembly is described within metadata. When code is executed, the runtime loads metadata into memory and references it to discover information about your code's classes, members, inheritance, and so on.
Metadata stores the following information:
1) Description of the assembly.
- The types available in that assembly, viz. classes, interfaces, enums, structs, etc., and their containing namespaces
- The types that are exported.
- Other assemblies that this assembly depends on.
- Security permissions needed to run.
2) Description of types.
- Name, visibility, base class, and interfaces implemented.
- Members (methods, fields, properties, events, nested types).
3) Attributes.
- Additional descriptive elements that modify types and members.
Manifest :-
The assembly manifest contains this assembly metadata. An assembly manifest contains all the metadata needed to specify the assembly's version requirements and security identity, and all metadata needed to define the scope of the assembly and resolve references to resources and classes. The assembly manifest can be stored in either a PE file (an .exe or .dll) with Microsoft intermediate language (MSIL) code or in a standalone PE file that contains only assembly manifest information.
Following information is store in an manifest
- Assembly name
- Version number - A major and minor version number, and a revision and build number. The common language runtime uses these numbers to enforce version policy.
- Information on the culture or language the assembly supports.
- Strong name information -The public key from the publisher if the assembly has been given a strong name.
- List of all files in the assembly
- Type reference information,this is used for types that are exported from the assembly.
Post a Comment