Re: [Mono-dev] Removing RabbitMQ

Hello, We cannot easily just remove the assemblies as that'd be quite bad breaking change but I'd be interested myself if there are any users of these very old assemblies. I am ok to deprecate them in the favour of nuget packages but the actual source code removal will have to wait. Marek On

Re: [Mono-dev] Old Mono.Cecil bundled in Mono tarball

Hello, > I notice that in mono master [2] cecil has been upgraded some weeks > ago to current master of cecil, which is version 0.10.0 Beta. > > I still would prefer if external libraries are not that hard bundled > into Mono, at least not delivered in the rpm. > I am trying to patch the bundled

[Mono-dev] CoreFX/CoreCLR dependencies

Hello, I'd like to share some plans we have for integration of more dotnet code. In 2014 we started replacing large chunks of Mono code with referencesource sources. This process has been going quite well and it has improved .NET compatibility and Mono quality significantly. Referencesource

Re: [Mono-dev] Problem with mcs build

That's just a warning you can safely ignore. What is more important is that basic.exe failed with error code which at this point looks like some sort of runtime error/problem. Marek ​ ___ Mono-devel-list mailing list Mono-devel-list@lists.dot.net

Re: [Mono-dev] Problem with mcs build

No, bootstrap process is not deprecated and it's still actively used especially when system mono is unavailable or too old. Marek On Tue, Oct 18, 2016 at 12:23 PM, Cyd Haselton wrote: > Ping for any input on pastebin logs (see previous emails) and if > bootstrapping mcs

Re: [Mono-dev] Problem with mcs build

t of sync? > > On Oct 19, 2016 10:01 AM, "Cyd Haselton" <chasel...@gmail.com> wrote: > >> The monolite files were included with the source tarball, so hopefully >> they are in line with the runtime. >> >> I can always run make get-monolite-late

Re: [Mono-dev] InvalidProgramException running .NET 4.0 app

Hello, > > One of the libraries uses System.Xml namespace from mono 4.0.0.0, I can > compile, but at runtime I get this system:InvalidProgramException: Invalid > IL code in System.Uri:op_Equality(System.Uri,System.Uri): method body is > empty [...] > This is most likely due to using reference

Re: [Mono-dev] Mono C# compiler switch

ther difference in debug symbols seems to me just too much. Marek > *From: *Mono-devel-list <mono-devel-list-boun...@lists.dot.net> on behalf > of Marek Safar <marek.sa...@gmail.com> > *Date: *Monday, November 28, 2016 at 9:46 AM > *To: *"Mono-devel-list@lists.dot.net

Re: [Mono-dev] Problem with mcs build

ch aren't very helpful >>> >>> On Oct 20, 2016 10:29 AM, "Cyd Haselton" <chasel...@gmail.com> wrote: >>> >>>> I ran gdb on the runtime by adding it to mono-wrapper; it runs without >>>> errors. >>>> >>>> On

Re: [Mono-dev] __MonoCS__ no longer defined?

This is not breaking change. __MonoCS__ is/was intended to be used for Mono C# compiler workarounds only [0]. It was never intended to be used for platform detection and we advertised it that way. Your code would break same way if someone compiled it on Windows and copied it over to non-Windows

Re: [Mono-dev] Mono 5 branches

Hello Jonathan, We still do branching but using different naming scheme, you can read more at http://www.mono-project.com/docs/about-mono/versioning/ The idea is to have fixed schedule and stabilization work happening regularly. So far we managed to do it on time so branch name could include the

Re: [Mono-dev] mcs error

Hi Neale, Most likely not, where do you see this error (or how can I reproduce it)? Thanks Marek On Sat, Nov 18, 2017 at 2:08 PM, Neale Ferguson wrote: > Is this a C#7 thing? The compile works with csc but not mcs: > > TaskRunner.cs(80,79): error CS0019: Operator `&&'

Re: [Mono-dev] MoMA

Hi Neale, Please submit PR to resolve the tests build issue. We'll merge it but we don't actively develop MoMA. Marek On Thu, Dec 21, 2017 at 4:05 AM, Neale Ferguson wrote: > Ah, I had just seen some activity on GitHub dated a couple of months ago > and seemed to recall

Re: [Mono-dev] How to compile mono.security.dll assembly with .NET 2.0

Hi Hugo, The easiest way for you is most likely starting with https://github.com/mono/mono/blob/master/mcs/class/Mono.Security/Mono.Security.csproj you could tweak that project to target .NET 2.0 framework and redo all assemblies references to use standard framework references. That way you get

Re: [Mono-dev] Why Create OutOfMemoryException will cause some data of sgen_cardtable be masked

Hello, I am cc-ing Vlad who can answer your question. Marek On Wed, May 9, 2018 at 7:41 AM, xiaozhu wrote: > hi,all > I'm doing some research of sgen_cardtable of the embeded mono. > And find that ,after the mono_jit_init_version call , some bytes of >

Re: [Mono-dev] mkbundle null reference exception with --deps option

Hello David, It'd be nice to figure out which assembly is causing this, you could build mkbuild from the Mono master with more logging. Alternatively, please fill a bug report at bugzilla.xamarin.com with the full repro which could be used to reproduce the issue. Thank you, Marek On Thu, Oct

Re: [Mono-dev] Build error

Hello, Indeed, I forgot to bump it as part of the latest corefx bump. Should be fixed soon. Marek On Thu, Jan 4, 2018 at 7:58 PM, Alexander Köplinger via Mono-devel-list < mono-devel-list@lists.dot.net> wrote: > Is this using system mcs or monolite? > > Actually @Marek I think we'll need to

Re: [Mono-dev] Building mono-core

Unfortunately, it’s still the case. It’s on their todo list but it has not been yet done. Marek From: Alexander Köplinger <alk...@microsoft.com> Date: Friday, 2 February 2018 at 14:35 To: Neale Ferguson <ne...@sinenomine.net> Cc: Marek Safar <mas...@microsoft.com>, Mono Devel M