[Mono-list] Swap out M$'s System.Data.SqlClient and substitute Mono's System.Data.SqlClient

[Mark Gimelfarb]

I would also like to know what you mean by a little bit buggy.

Right now, the bugs I'm experiencing with the M$'s implementation are
preventing me from deploying a mission-critical apps. For those of you
familiar with the problem, I'm talking about General Network Errors and
a situation where MS's SqlClient drops the connection when it receives
ACK+RESET bits set on the packet, in the case when the response is
broken into several packets. So far, M$'s response was to set the
CommandTimeout to 7200, which is definitely is a workaround, not a
solution.

I would rather use Mono's implementation, because of the managed
TdsClient, rather than M$'s reliance on dbnetlib.

When I tried to compile the latest CVS System.Data under cygwin, it
turned out that I also needed System.Security in addition to Mono.Tds.
Is that also a requirement? I wonder if I should just get the latest
stable DLLs from the Windows installer of Mono? I'd rather use the CVS
version, if I can convince the build scripts to build it for me :)

Thanks in advance.

Regards,
	Mark.




On Thu, 2004-12-16 at 10:17 +0100, Aleksandar Dezelin wrote:
> Daniel Morgan wrote:
> 
>  > 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 in
>  > 100% C#.
>  >
>  > If System.Xml.dll and System.EnterpriseServices.dll do not work for 
> you, you
>  > may need to use Mono's too.
>  >
> 
> I've tried that and it worked for me. You must also use Mono.Data.Tds.dll.
> 
> I think it's little bit buggy.
> 
> 
> Cheers
> Aleksandar Dezelin
> 
> 
> -- 
> Linux is like wigwham - no windows, no gates, and apache inside...
> 
> 
> 
-- 
Mark Gimelfarb <mark@dawebber.com>