RE: Don't compile libmysqld.dll (Embedded MySQL) with VS.NET - Matt Solnit - com.mysql.lists.win32

7 messages in com.mysql.lists.win32RE: Don't compile libmysqld.dll (Embe...

From	Sent On	Attachments
Matt Solnit	15 Nov 2002 09:17
Dennis Salguero	15 Nov 2002 16:31
Joseph D. Wagner	15 Nov 2002 19:15
Matt Solnit	18 Nov 2002 08:42
Matt Solnit	18 Nov 2002 10:11
Dennis Salguero	18 Nov 2002 14:35
Matt Solnit	18 Nov 2002 17:58

Subject:	RE: Don't compile libmysqld.dll (Embedded MySQL) with VS.NET
From:	Matt Solnit (msol...@iteration.com)
Date:	11/18/2002 08:42:08 AM
List:	com.mysql.lists.win32

Josh, Dennis,

I think you have both misunderstood me. It's not an issue of managed vs. unmanaged. In fact, in either case it's an unmanaged library and a managed client, and in one case, it works, and in the other, it doesn't. The issue is using the right compiler to build the library. For some reason, if I compile it with the C++ compiler included with VS.NET, then the library doesn't work. If I use the older C++ compiler included with VS 6.0, then everything is fine.

-- Matt

That's because libmysqld.dll hasn't been ported to the Microsoft .NET Framework.

A lot of old components from Visual Studio or Visual C++ 5.0/6.0 simply won't work with Visual Studio .NET 2002. You have to upgrade those outdated components to the .NET Framework.

Uhm, not necessarily. There are wrapper utilities within VS.NET that you can use for dlls and COM components written in non .NET languages. This will create "new" DLLs that you can then use as a reference within another native .NET project.