----------------------------------------------------------- New Message on BDOTNET
----------------------------------------------------------- From: [Bhavtosh. S] Message 2 in Discussion Hi, this will make u little clear abt what is: Metadata: -Metadata is binary information describing your 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 your 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. Manifest: well manifest contains the following info: Assembly name A text string specifying the assembly's 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. Culture Information on the culture or language the assembly supports. This information should be used only to designate an assembly as a satellite assembly containing culture- or language-specific information. (An assembly with culture information is automatically assumed to be a satellite assembly.) 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 A hash of each file contained in the assembly and a file name. Note that all files that make up the assembly must be in the same directory as the file containing the assembly manifest. Type reference information Information used by the runtime to map a type reference to the file that contains its declaration and implementation. This is used for types that are exported from the assembly. Information on referenced assemblies A list of other assemblies that are statically referenced by the assembly. Each reference includes the dependent assembly's name, assembly metadata (version, culture, operating system, and so on), and public key, if the assembly is strong named. And as fasr test.exe is concerned, its hard to assume that the contents of the exe will be same in both vb and vb.net, since the way the info of exe is made available might not be the same. if anyone also share the views on this, it would be nice ! [Bhavtosh] ----------------------------------------------------------- To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings. http://groups.msn.com/BDotNet/_emailsettings.msnw Need help? If you've forgotten your password, please go to Passport Member Services. http://groups.msn.com/_passportredir.msnw?ppmprop=help For other questions or feedback, go to our Contact Us page. http://groups.msn.com/contact If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list. mailto:[EMAIL PROTECTED]
