Legacy VC 6 libraries compatable with .NET??
-
I switched from Visual C++ 6 to a C# .NET solution. In my original VC 6 project I was linking a .lib file to my code. The .lib was providing me some functions to a CORBA orb. This .lib file doesn't seem to be working with my new .NET project. Does anyone know if you can use libraries coded in legacy VC++ 6 with the new .net framework or do I have to rewrite the libraries in C# .net as well? Thanks, Zahid Regards, Zahid
-
I switched from Visual C++ 6 to a C# .NET solution. In my original VC 6 project I was linking a .lib file to my code. The .lib was providing me some functions to a CORBA orb. This .lib file doesn't seem to be working with my new .NET project. Does anyone know if you can use libraries coded in legacy VC++ 6 with the new .net framework or do I have to rewrite the libraries in C# .net as well? Thanks, Zahid Regards, Zahid
You should be able to, but I don't know how. Kevin
-
I switched from Visual C++ 6 to a C# .NET solution. In my original VC 6 project I was linking a .lib file to my code. The .lib was providing me some functions to a CORBA orb. This .lib file doesn't seem to be working with my new .NET project. Does anyone know if you can use libraries coded in legacy VC++ 6 with the new .net framework or do I have to rewrite the libraries in C# .net as well? Thanks, Zahid Regards, Zahid
I have many VC 6 libraries that just work in both the 2002 and 2003 Visual Studios. Now, you didn't mention, but your still compiling C++ code, right? The C# or VB.NET stuff won't be able to use those libs. If you still can't get the libs to work, how about listing what the errors are? Perhaps something might need some tweaking. -- Joel Lucsy
-
I switched from Visual C++ 6 to a C# .NET solution. In my original VC 6 project I was linking a .lib file to my code. The .lib was providing me some functions to a CORBA orb. This .lib file doesn't seem to be working with my new .NET project. Does anyone know if you can use libraries coded in legacy VC++ 6 with the new .net framework or do I have to rewrite the libraries in C# .net as well? Thanks, Zahid Regards, Zahid
Some header includes are now officially redundant in 2003 so Microsoft is more 'ANSI compatible' and portable. If these lib headers include some now redundant libraries, you will have problems. A colleague of mine had linker errors. If these circumstaces sound familiar then changing your projects build order is needed to remove them. Al. "When I left you I was but the learner, now I am the master" - Darth Vader