Actually I'm working on application obfuscation (i.e. a closed set of assemblies) - for example, an EXE plus its set of private assemblies. I guess this is meta-obfuscation. <g> I can obfuscate all public members as long as I chase down all references in the client assemblies and update them appropriately.
-- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -----Original Message----- From: Serge Lidin [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 2:53 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Partition II Metadata Spec question Of course you can have foreign TypeRefs, which are resolved by full name (namespace.name). TypeRefs are always resolved to TypeDefs by full name. Resolution scope only indicates in which TypeDef table this full name should be sought. For example, if TypeRef has a ModuleRef as the resolution scope, the TypeDef table of respective module must contain a record with the same full name. The only "domestic" TypeRefs are those with resolution scope 1 -- it means there must be a TypeDef table entry with the same full name in this very module. But the ref-to-def resolution is done by the Loader, and I don't see why you should concern yourself with anything but "domestic" TypeRefs. Or did I misunderstand your question? Thanks, Serge You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
