How can I use a dll created in Visual Basic 2008 in Visual Basic 6.0

Question

0.00/5 (No votes)

See more:

I create a dll in visual basic 2008 but when trying to register on a computer with Visual Basic 6.0 (regsvr32), throw an error about a missing module.

Please help

Posted 29-Jun-11 5:04am

pepito del puerto

Updated 29-Jun-11 5:05am

v2

Add a Solution

3 solutions

Solution 2

It seems that you're library uses a control or .DLL that isn't present on the customer machines. What external .DLL's is your library using?

Posted 29-Jun-11 6:52am

Dave Kreskowiak

Comments

pepito del puerto 29-Jun-11 13:04pm

My dll doesn't use any other dll, only the code of the class itself

Dave Kreskowiak 29-Jun-11 13:15pm

Did you register your .DLL on the client machine with REGASM?? RegSvr32 doesn't work on .NET COM-exposed .DLL's.

Solution 3

Packaging .NET assembly as COM component works, but it has many downsides. There are more effective techniques which allows to directly export managed methods as unmanaged, so the .NET assembly could be used by the unmanaged code like any other unmanaged DLL, for example, by VB.

It is commonly believed that this is impossible. But this is not true. It is only impossible in C# or VB.NET, but quite possible using IL assembler; and this is a part of CLR ECMA and ISO standards, not like any dirty trick.

So, the idea is to use a special attribute to mark the methods to be exported as unmanaged. The code is complied by VB.NET or C#, disassembled; then the IL code is modified according to the attributes and assembled again. This is automated using the MSBuild custom step, so no knowledge of IL assembler is required.

You can find the solution in the following CodeProject articles:
Unmanaged code can wrap managed methods[^],
How to Automate Exporting .NET Function to Unmanaged Programs[^].

—SA

Posted 30-Jun-11 12:59pm

Sergey Alexandrovich Kryukov

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)

Dylan Morley · Accepted Answer · 2011-06-29T05:05:00

Solution 1

Read this article, make sure you have implemented all of the required steps

Exposing .NET Components to COM[^]

Posted 29-Jun-11 5:05am

Dylan Morley

Comments

pepito del puerto 29-Jun-11 13:07pm

I will try this method, I mention the results when I have it

Sergey Alexandrovich Kryukov 30-Jun-11 19:00pm

That is the solution, my 5.

However, an alternative solution exists: direct export as unmanaged. Don't say it is impossible; please first read my solution and referenced articles -- very interesting.

--SA