Regarding the TcpClient timeouts, if you are setting the timeout before
connecting, it is ignored. That is a bug. See
https://bugzilla.xamarin.com/show_bug.cgi?id=25365. As a workaround you can
set the timeout after connecting.
On Mon, Jan 26, 2015 at 11:12 PM, Edward Ned Harvey (mono)
On 27.01.2015 18:56, Edward Ned Harvey (mono) wrote:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Robert Jordan
You may want to look up how a sane IDisposable pattern has to be
sensibly implemented in .NET. You'll find out that
Hi,
It is not intended to limit to rabbitmq. Patches are welcome to make it
to work with other providers :-) It just shouldn't be too extensive to
add another MQ binding or implementation in mono repo either as sources
or submodule. Hard-coded, run-time resolution to assemblies that don't
+1, now that the community edition provides easy access to a current VS for
open source devs I see no reason to keep the old stuff.
-- Alex
Date: Tue, 27 Jan 2015 21:15:46 +
From: direct...@apebox.org
To: mono-devel-list@lists.ximian.com
Subject: [Mono-dev] Visual Studio project files -
Dear all,
We're currently considering upgrading the Visual Studio project files
for the Mono runtime to require VS2013 as a minimum, rather than 2012.
This introduces two major features for us - it means C99 compatibility
so we can clean up the runtime to use standard C99 types throughout, and
Anything that makes it possible for Windows developers to build mono and
run its tests so we can contribute more would be good. We use VS2010
exclusively in our work with Mono - with Resharper it does everything we
need, so we've never bothered to upgrade. Having the community edition of
2013
On Jan 27, 2015, at 3:22 AM, Atsushi Eno atsushi...@veritas-vos-liberabit.com
wrote:
Hard-coded, run-time resolution to assemblies that don't exist in mono
itself would be fine
Are you saying that _only_ hard-coded resolution is acceptable? My intent was
to allow the user to specify any
From: Greg Najda [mailto:gregna...@gmail.com]
Regarding the TcpClient timeouts, if you are setting the timeout before
connecting, it is ignored. That is a bug. See
https://bugzilla.xamarin.com/show_bug.cgi?id=25365. As a workaround you
can set the timeout after connecting.
Client-side,
On 27.01.2015 15:46, Edward Ned Harvey (mono) wrote:
The question still stands about what happens if Dispose() hangs during garbage
collection...
You may want to look up how a sane IDisposable pattern has to be
sensibly implemented in .NET. You'll find out that Dispose()
shouldn't be
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Robert Jordan
You may want to look up how a sane IDisposable pattern has to be
sensibly implemented in .NET. You'll find out that Dispose()
shouldn't be called from a finalizer.
10 matches
Mail list logo
