Including a visual c++ 6.0 header file in Visual C++ 2010 project

Question

1.00/5 (2 votes)

See more:

Hello,

I have a visual C++ 2010 prj. I have two other old prjs complied in VisualC++ 6.0 and I want to use these old prjs classes in the new one. I was able to add one of the old prjs successfully by setting the linker options, adding path in additional include dirs and including the header file. I can create objs for classes and call methods successfully.
But for the second one, once I Include the prj and build my solution in vc++ 2010, I am getting a lot of errors. The prj compiles successfully in vc++ 6.0.

Is there a way I can include this prj successfully or Do i have to resolve each of these errors? I I see the errors growing as I keep resolving.

Thanks
R S

Posted 9-Jul-13 3:27am

_R_S_

Add a Solution

Comments

KarstenK 9-Jul-13 9:51am

You have to include these error messages!!!

Sergey Alexandrovich Kryukov 9-Jul-13 10:39am

Just one note: the number of errors does not grow as you resolve some. Rather, the modification you have done in code, cannot be called "resolution". But I know, the build of many legacy units, especially in C++, can be quite painful. Why do you think a quick answer can possibly help you? This is just work... First of all, think if you really want to go through all that...
—SA

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)