.NET Core support

Hey,

Do you have any plans to port to CoreClr? Happy to help out if there is buy-in etc.

UPD1: prerelease NuGet feed: https://ci.appveyor.com/nuget/rabbitmq-dotnet-client-ci
UPD2: RabbitMQ.Client releases on NuGet are now .NET Core compatible.

[michaelklishin]

Duplicate of #103.

We already have a WinRT port which ended up reusing most of the code, so I'd be interested in seeing how difficult can it be to support CoreCLR.

I should have some free time over the weekend, so i'll pull down the code and have a go at porting it for you. Will report back with my findings.

[jeremymeng]

@sblackler How is it going? I attempted the port too as a hobby: master...jeremymeng:CoreClr. Both client and unit test project build. I attempted to run the tests but it seems like I don't have the rabbitmqctl so the test process crashed on me. Anyway hope this is helpful to anyone who wants to continue working on it.

[michaelklishin]

@jeremymeng thank you. If you can explain what kind of environment is necessary to give it a try (I have Windows 8.1), I can do it.

[michaelklishin]

@jeremymeng the changes look smaller than I thought, this is encouraging. Note that I'm afraid we can't license parts as MSPL and to integrate your changes eventually we'd have to ask to you sign our CA.

[jeremymeng]

thank you. If you can explain what kind of environment is necessary to give it a try (I have Windows 8.1), I can do it.

VS 2015 Community Editor with update 1 should be good. For command-line only experience, you can install ASP.NET 5 RC as described at https://docs.asp.net/en/latest/getting-started/index.html.

I now use the code from Stephen's blog so there should be no license involved.

[theparticleman]

@ru-sh has created a fork that targets CoreCLR that I've been using (he also has an unofficial NuGet package). It has a bug where trying to connect via IPv6 throws an unexpected exception type, so then it doesn't try connecting via IPv4. Once I fixed that it would connect from my Windows client host to my Rabbit running on my Linux Vagrant guest. But going from a Linux Vagrant client to Rabbit running on another Vagrant client hangs. Haven't gotten farther than that yet.

Here's a link to his fork: ru-sh@ffedb32

[doc]

Hey Guys, any updates on this port? Keen to see support for .net core arrive so happy to help in any way I can.

[michaelklishin]

No updates besides that we've decided it should be a completely new client.

On 26 mar 2016, at 3:03, Mark notifications@github.com wrote:

Hey Guys, any updates on this port? Keen to see support for .net core arrive so happy to help in any way I can.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub