TheSwamp

Code Red => .NET => Topic started by: Keith™ on March 10, 2008, 10:37:40 AM

Title: Deployment of .NET dlls
Post by: Keith™ on March 10, 2008, 10:37:40 AM

Ok, I have a few questions regarding the deployment of .NET dlls

I have created a .NET COM dll that can be accessed via VB(a) so that programs that do not use .NET natively may use the .NET assembly via their VB(a) interface.

On several of the builds I have multiple files in my release\bin folder. For example if the dll is called foo.dll, I will also have foo.tlb (type library) and a seemingly random named interop.xxxxx.dll, presumably corresponding to the interops used in the program.

1) Do I need to distribute all of the files i.e. foo.dll, foo.tlb and interop.xxxxx.dll ?

2) Is there any way using software such as InnoSetup or Installshield to register foo.dll (other than calling RegAsm.exe)

3) Is the registration of interop.xxxxx.dll required or possible

4) Is the registration of foo.tlb required or possible

Title: Re: Deployment of .NET dlls
Post by: MaksimS on March 13, 2008, 07:23:57 AM

InstallShield, staring from version 11 I guess, supports managed assemblies' registration (either with GAC or via interop). You can keep all the assemblies in one folder if you're not planning to sign them and register with GAC.

Regards,
Makism Sestic