vb6 dll usage in vb.net

Question

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 13-Jul-12 2:28am

Member 9029878

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Dave Kreskowiak · Accepted Answer · 2012-07-13T03:50:00

Solution 1

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.

Posted 13-Jul-12 3:50am

Dave Kreskowiak

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.