Scripting

Here are five methods to accomplish this task:

1. In the Setup Design view, right-click the desired feature and select Component Wizard. Browse to the file, add it and select the Extract COM Info Immediately checkbox. Then complete the Component Wizard.
2. In the Setup Design view, click the component that contains the DLL and set the COM Extract at Build property to Yes.
3. In the Setup Design view, click the component that contains the DLL, expand the Files node, right-click the key file and select Extract COM Data for Key file.
4. In the Setup Design view, click the component, expand the Files node, right-click the key file, select Properties, then select the Self-Register checkbox. Be sure to click Apply, then OK.
5. In the InstallScript view, you can do manual registration by calling regsvr32.exe. If you are doing this from an InstallScript custom action in a Basic MSI project, you may need to set the custom action to Deferred in System Context.

here's another great document about the whole concept behind this "COM Registration"  and how you can optimize your package ( wthout a lot of "garbage registry")

Thank You I will try it and confirm Jdornan

Hi, Jaybee, The 2 and 3 procedure of the doc is not working for me, can anyone please look into it and let me know what is wrong with my package

Hi, I am back onto this thread.

I am able to register .ocx and able to make it work perfectly but here is the issue.

I installed it and it is running fine. Then Uninstalled it. Then reinstalled it, then I get the error

"could not connect to the key clsid\inprocserver32 verify that you have sufficient access to that key"

So, it is not uninstalling perfectly, is there any solution in how to do that.

Regards