I've created a C# COM Interop Dll which inteferces with ASP and a 3rd Party .NET assembly. On my local machine .NET takes care of the registration of the component and ASP knows how to create the Component and everything works great. When I deploy this to another server it doesn't seem to work and the Server.CreateObject function gets an error while trying to create the component. Does anyone know how to register the COM interop Dll on a remote server so that ASP can create the DLL? Is there anything special I need to do when moving the 3rd party DLL to the server?

Register the 3rd party Dll on the server, if its not already.
Just execute this command on the command prompt on the server

regsvr32 <your3rdParydllwithpath.dll>

If you are responsible for deploying the app,
it would be best if you include the registeration
process in the setup.

Regards
Ankur Verma

Figured it out.

Needed to run gacutil /i <DLL path/file> for my component
              gacutil /i <DLL path/file> 3rd party .NET component
              regasm <DLL path/file> /regfile on my dll and creates
as regsitry file. Run the registry file loading the data to the registry. Make sure to run iisreset and it worked.

If you have the 3rd party Dll with you, which i believe is a COM
dll then you dont have to go thru all that. You are sort of reversing
the process here to register a component for which you also have a RCW
(Runtime Callable Wrapper). Although its working for, do explore the
shorter route as well.

Regards
Ankur

You can run regasm.exe against the dll using the /regfile option. try regasm /? at the VS command prompt for exact syntax. This creates a registry file which can be run on the target machine and makes it appear to the machine that the assembly is a COM class.


--

Joe (Microsoft MVP - XML)