Thanks. I would be coding in C# here. I do think I could manage to initialize
on first use of a contained class. But there may well be a substancial delay
between this DLL being loaded and a class inside it actually getting used. So I
was hoping that (a) I could use that time to do some work and (b) that if there
was some initialization error it could be reported sooner rather than later.
>Thanks. I would be coding in C# here.
OK, it doesn't support defining a module initializer.
>I do think I could manage to initialize
>on first use of a contained class. But there may well be a substancial delay
>between this DLL being loaded and a class inside it actually getting used.
Where's the DLL being loaded from? Keep in mind that the CLR doesn't
load assemblies until they are needed, so unless the client explicitly
uses something like Assembly.Load it will not be loaded in advance.
Mattias

Signature
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.