C++ v6 Visual Studio and Visio Studio .NET compatibility

I have an application to program in C++.  The application documentation calls for v6 of Visual Studio.

Can I use the latest version of .NET Visual Studio?  ( http://msdn.microsoft.com/vstudio/se/ )

Will there be any compatibility issues? I must use precompiled DLLs from the vendor.

Is there a v6 mode in .NET Visual Studio?

Any other issues to watch out for?

Thanks for the help.

Chuck W
watsocdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AxterCommented:
>>The application documentation calls for v6 of Visual Studio.

Yes, you can use .Net
It's more compliant with the standard then VC++ 6.0


>>Is there a v6 mode in .NET Visual Studio?
No

>>Any other issues to watch out for?
As long as your code is compliant with the C++ standards, you shouldn't have to worry about using .Net VS 6.0
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
waysideCommented:
VC 6.0 and VC.Net use different versions of the runtime libraries. Mixing these within the same program could lead to problems. For example, if the dll creates something using (vc 6.0) new and your program deletes it using (vc.net) delete, this willl probably cause a crash.

I don't remember if the name mangling changed from vc 6.0 to vc.net, but if it did, and the dll's export mangled names, you won't be able to link.

0
guntherothkCommented:
The default settings vor VC 7 (.NET 2003) flag code that would be a problem using a 64 bit processor, typically assumptions that a pointer is the same length as an int. This generates a lot of warnings from certain kinds of code. While these warnings are meaningful, they don't stop your 32-bit code from working.

You have to tell VC7 not to produce managed code, as this is the default.

The problems dll compatibility problems mentioned by wayside are real, but they are only a potential problem, not one that occurs frequently or always. It's worth trying, but keep this problem in the back of your head if you get an intractible bug.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C++

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.