Registration of .ocx and dll and dotnet dll

COM files must be either self registered or you must use the "COM extract at build" option as xinjiang states. The latter is generally preferred since it will allow MSI to properly clean up and or reference count the registry data since the registry data is then added to the MSI itself. Self registration is done by each file on its own, and MSI then has no control of what registry entries are added. COM files can be either DLL, OCX or EXE (the latter being an out of process COM server, and may need special handling. it can be registered by APP.EXE /RegServer from the command line).

.NET assemblies are generally easier. If they are private assemblies no registration is needed. If they expose themselves for COM Interop you need to enable the "COM Interop" setting in the component. This registers the .NET assembly so that it can be called by another COM component. If you are dealing with public assemblies they should be installed to the GAC if they are indeed used by different applications. Installation to the GAC requires strong file names (read the SDK for more info on this).

Win32 files generally does not require any registration (unless it is a service).

asrinivas

xinjiang

Glytzhkof