Using dlls built in VC6 in project wrote .net

G

Guest

I try to build dll in VC .NET,
In that project I use dlls that were built in VC6, and I get a lot of errors.
(for example <iostream.h> instead of <iostream> etc.)
I am not aloud to change anything inthe code of projects that were built in vc6.
I need to make it works together(dlls that were built in vc6 and the one that was built in .NET).
The main problem is that the vc6 header files that were included in .net source code raise such errors of names of headers files that are different from 6 to .NET,
or dlls that are not found in .net and do in vc6.
Does anyone know a solution to that problem?
Does it depends on the project type that I open?
Thanks in advance
Keren



**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
 
M

Martin Richter [MVP]

Hallo !
I try to build dll in VC .NET,
In that project I use dlls that were built in VC6, and I get a lot of errors.
(for example <iostream.h> instead of <iostream> etc.)
I am not aloud to change anything inthe code of projects that were built in vc6.
I need to make it works together(dlls that were built in vc6 and the one that was built in .NET).
The main problem is that the vc6 header files that were included in .net source code raise such errors of names of headers files that are different from 6 to .NET,
or dlls that are not found in .net and do in vc6.
Does anyone know a solution to that problem?
Does it depends on the project type that I open?

The STL headers with the .h extension are deprecated. Even in VC6 you
should use the files without an extension, and if needed add using
namespace std;
 
C

Carl Daniel [VC++ MVP]

I try to build dll in VC .NET,
In that project I use dlls that were built in VC6, and I get a lot of
errors. (for example <iostream.h> instead of <iostream> etc.)
I am not aloud to change anything inthe code of projects that were
built in vc6.
I need to make it works together(dlls that were built in vc6 and the
one that was built in .NET).
The main problem is that the vc6 header files that were included in
.net source code raise such errors of names of headers files that are
different from 6 to .NET, or dlls that are not found in .net and do
in vc6.
Does anyone know a solution to that problem?
Does it depends on the project type that I open?


The solution is to do everything in using a single version of VC++, be it
VC6, VC7 or VC7.1. When you have a DLL that exposes C++ standard library
classes in it's API it's simply not possible to mix compiler versions. If
you can't change the code of the existing DLLs and rebuild them, then you'll
need to do everything in VC6.

-cd
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top