Click here to Skip to main content
15,041,393 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
if a custom vb6 dll is used in vb.net on a windows 7 machine, do you have to register it on each pc which the application runs on? How do I include it in the distributed build?
Posted

1 solution

Since VB6 could only target building COM-based .DLL's, yes, you do have to register it on the machine it's being used on.

If you build a REAL installer for your application (Windows Installer type), using a REAL installation build application (like InstallShield, InnoSetup, Advanced Installer, WiX, ...), registering the component is done for you automatically.
   
Comments
Member 9029878 13-Jul-12 10:03am
   
I am just learning vb.net. When you say REAL installer does that include publishing it to an url and installing from the url?
Dave Kreskowiak 13-Jul-12 13:16pm
   
Publishing it to a URL has nothing to do with packing the application into an installer.

But, since you mentioned it, I take it you're using ClickOnce? Yeah, not a real installer. Though, it'll still include your component and register it properly, ClickOnce puts severe limitations on what you can and cannot do in your application and your deployment choices.
Member 9029878 13-Jul-12 13:01pm
   
Thanks for the info, I do appreciate your input.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900