[Mono-list] Swap out M$'s System.Data.SqlClient and substitute Mono's System.Data.SqlClient
Tue, 14 Dec 2004 22:50:46 -0500
Sure. You can build it with csc and run it on .NET.
You will need Mono.Data.Tds.dll too which implementes the TDS protocol =
If System.Xml.dll and System.EnterpriseServices.dll do not work for you, =
may need to use Mono's too.
[mailto:email@example.com] On Behalf Of Mark Gimelfarb
Sent: Tuesday, December 14, 2004 6:16 PM
Subject: [Mono-list] Swap out M$'s System.Data.SqlClient and substitute
I got asked this by one of the developers working with me: "Can I
just swap out the Microsoft's System.Data.SqlClient and use Mono's
instead?". This particular developer has been having issues with MS's
implementation of SqlClient namespace and would like to see he can =
them by using Mono's implementation, which is 100% managed (MS got a
unmanaged layer hooking into dbnetlib from what I understand).=20
So, my question to you guys is: "Can I just build a stand-alone version =
Mono's System.Data.dll with csc and substitute it instead of MS's
I understand that some of the stuff System.Data does are =
but since corlib b/w Mono and MS.Net are API-compliant, I was thinking =
it was possible to do that.
Obviously, the references will have to be adjusted for the application
project to work properly, but that isn't an issue.
The app in question is an ASP.NET app, even though I don't think it's
relevant in this case. And no, it can't run under XSP yet, as some of =
third-party controls it's using don't work with XSP yet.
Thanks in advance.
Mark Gimelfarb <firstname.lastname@example.org>
Mono-list maillist - Monoemail@example.com