I'm developing MS Office COM Add-ins using C# and VB.NET. These work fine when registered at installation time with REGASM. However, Office COM Add-ins can also be loaded manually by the user through a dialog box. However, when you attempt to manually load a .NET dll you get the message "xxx.dll is not a valid Office add-in" since there is no DLLRegisterServer DLL entry point exposed.
I'd like to be able to support manual loading of my COM Add-ins. Is there any mechanism that would support injecting these DLL entry points into a .NET Assembly DLL? I presume this would be possible with Managed C++ but I'd like to stick to C# and VB.NET. A few weeks ago I thought I saw a reference to a technique for embedding the typelib as a Win32 resource, but I can't seem to locate it any more. Hopefully, someboy can point me in the right direction. Thanks, - Mike You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
