"Version 2.0 is not a compatible version." from VB6

Question

0.00/5 (No votes)

See more:

We have a COM module written in VC++ 6.0 which is called from both VC++ 6.0 and VB 6.0 programs. As an early step in moving to .Net, this module was rewritten as a .Net 3.5 assembly with a thin COM module wrapper which is still called from VC++ 6.0 and VB 6.0 programs (these programs are unchanged). The VC++ 6.0 programs work exactly as expected, but the VB 6.0 program gets a "Version 2.0 is not a compatible version." error when attempting to use the COM module/.Net 3.5 assembly.

Installed versions of .Net frameworks 2.0, 3.0 and 3.5 have been verified. The machine running the programs has Windows Server 2003 - R2 installed.

Any ideas what could be missing or broken in the environment? Can anyone at least clarify what "Version 2.0 is not a compatible version." means?

Posted 29-Nov-11 3:44am

Phre2d

Updated 29-Nov-11 9:13am

v4

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)

#realJSOP · Answer 1 · 2011-11-29T04:55:00

Solution 1

I think I remember hearing something about having to install versions of .Net in the proper order. Maybe the new server was installed from a newer disc, and had .Net 3.5 on it, and .Net 20 was installed as an afterthought? You might want tto try uninstalling both versions, and then reinstalling in version order.

No guarantees, though.

Posted 29-Nov-11 4:55am

#realJSOP

Comments

Phre2d 29-Nov-11 15:32pm

Thanks for the suggestion, but it doesn't seem to be the problem.