On Thu, Mar 26, 2015 at 9:41 PM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Gelin Yan
A few years ago, I tried to port one of our server from .net to
As an aside I was perf and stability testing some code last night and mono
used less memory and was faster than the equivalent clr tests. Good job
everyone :)
On Thursday, March 26, 2015, Gelin Yan dynami...@gmail.com wrote:
Hi All
A few years ago, I tried to port one of our server from
From: Gelin Yan [mailto:dynami...@gmail.com]
Unfortunately, at the time, mono crashed each time after a few seconds of
pressing tests. (IAsyncResult was slightly better,
it lasted a bit longer).
Check the mono compatibility guide. All the async stuff, except for ASP.Net,
has stabilized
I am running into this on a build ubuntu 14.14 box bootstrapped with
3.12.1 (first pull down of sources)
MCS [net_4_5] mono-symbolicate.exe
MDOC[net_4_5] cs-errors.tree
Error destroying handle 0x40d mutex due to 16
Stacktrace:
at unknown 0x
at (wrapper managed-to-native)
Hello,
I was under the impression that there were different versions of the
MSBuild API?
But I guess we implement the right one?
My main concern was not breaking MonoDevelop, so if we do not break it, we
should be fine.
Let me know when you think you are ready, and we should incorporate
probably, 3.12.1 is still unstable. i'm using 3.0.8 on OpenSUSE 13.2
and works fine (small glitches not counting..)
it better for now to use mono stable for daily use
André
Greg Young schreef op 27-3-2015 om 14:59:
I am running into this on a build ubuntu 14.14 box bootstrapped with
On 27/03/15 13:59, Greg Young wrote:
I am running into this on a build ubuntu 14.14 box bootstrapped with
3.12.1 (first pull down of sources)
Which specific commit?
We run CI builds of Mono, and should be able to tell you whether a given
commit is known-bad or not.
Hello Lluis,
I think once we are happy with msbuild, that we should build msbuild as
part of the standard Mono build process and ship the resulting libraries
and script.
My only concern is whether the public API surface that msbuild has is able
to replace the assemblies that we currently install
