Depending on how complicated the API is, here is one approach that would work
Write a "C" wrapper library to your C++ API and build this with VC++ 6.0. You should then be able to link to this VC6.0 "C" library from VS2005 since the name mangling for "C" is unchanged and there are no C++ class layout issues to be concerned about Andrew -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Eddie Lascu Sent: Thursday, July 20, 2006 8:47 AM To: [email protected] Subject: [Spam:***** SpamScore] Re: [ADVANCED-DOTNET] Linking an unmanaged C++ .dll in a VS.NET 2005 Managed C++ Class Library Yes Andrew, you were right, it didn't work. I will try to ask for a VS2005 compiled library, but I have little hope that this is going to happen. It's a bank I am dealing with and the ".dll" is my access interface for Point-of-Service transactions. Thanks for your answers. Regards, Eddie -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Eames, Andrew Sent: Wednesday, July 19, 2006 4:21 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Linking an unmanaged C++ .dll in a VS.NET 2005 Managed C++ Class Library You'll need to bracket your inclusion of the library header file with #pragma unmanaged But I'm betting that won't be enough.... My recollection is that the symbol mangling changed from 6.0 to 7.0. If it is a C++ Dll you probably want to try and get the third party to rebuild a version for VS2005 for you Andrew -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Ritchie Sent: Wednesday, July 19, 2006 3:56 PM To: [email protected] Subject: [Spam:***** SpamScore] Re: [ADVANCED-DOTNET] Linking an unmanaged C++ .dll in a VS.NET 2005 Managed C++ Class Library Is this a Visual Studio 2005 generated LIB file? Visual Studio is notoriously bad for supporting LIB files generated with a different Visual Studio version, especially LIBs for DLLs. On Wed, 19 Jul 2006 14:54:29 -0400, Eddie Lascu <[EMAIL PROTECTED]> wrote: >Hello Experts, > >I have this third party .dll that was developed in Visual C++ 6.0. I have >the ".lib" file and also some header files to include in my project. I am >trying to wrap it into a Managed C++ Class Library developed in Visual >Studio.NET 2005. I picked Managed C++ because I read the interoperation is >easier from C++ than C# or VB.NET. >Anyway, I am getting linkage errors for virtually every call into the >library (LNK2028 paired with LNK2019). I have linked the ".lib" file and >made sure the ".dll" file is found in the local folder, but I still get >these linkage errors. >This library is quite old and I had to make some changes in the header files >to make them compile. I read about the myriad of compilation/linkage >directives and I am at loss with them. > >Are there any web recourses to guide me through all the steps that need to >be followed to get this to compile and link? >Any suggestion will be appreciated, =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
