> Not knowing anything about META.INF or MANIFEST.MF, or much > about Java, it's my impression that .Net "attributes" are the > place where some such things would be stored. Not > necessarily the ones that you show in your example, however. > > Info about the OS and the processor are not needed (as .Net > code is always in MSIL format); in theory (not sure about > practice) a .Net app built on 32-bit Windows (XP for example) > should run unchanged under Mono on 64-bit Linux.
The custom info in my example was describing native code libraries required/used by a bundle/assembly. [Bundle is approx== Assembly + custom information in manifest] > Attributes provide a class-based mechanism that allows you to > tag various code elements (assemblies, methods, parameters, > ...) with arbitrary info that's available at runtime. Custom attribute classes were my first option. I am worried the resulting system would be inflexible since changing a bundle's "Bundle-Category" attribute would now require a rebuild of the otherwise unchanged source code. Is there a way round this on the CLR? Another consideration is that some bundles have no exectuable code. Perhaps just resources. But the may still have the custom info in the manifest too. Kunle =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
