Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Any plans to supports .NET Core?

See original GitHub issue

Hi guys,

  Our program used the EasyNetQ to finish many businesses,
  Has there any plans to support the .NET Core in the further time?
  I hope so, because the JSON.NET has done with it.

thanks a lot, Kevin Yang

Issue Analytics

State:
Created 7 years ago
Comments:10 (9 by maintainers)

Top GitHub Comments

1reaction

radicalgeekcommented, Jul 3, 2016

There was a fork that I have had working with dnxcore50 https://github.com/SapientGuardian/EasyNetQ

Now that netcore1.0 is supported in the Master branch of RabbitMQ.Client, https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/148 and available in the pre-release feed, I am going to try compiling that fork against netcore1.0 this week if I can find the time.

I am also very very keen to see EasyNetQ support for netcore, our current system uses RabbitMQ at it’s core with mono services on linux, so I am looking forward to getting a good netcore service running so I can compare it with our mono ones.

0reactions

radicalgeekcommented, Jul 4, 2016

ok, I have it compiling on my fork (of a fork, so no idea how behind it is). You can find it here https://github.com/radicalgeek/EasyNetQ . Last time I did this a couple of months ago core dnxcore50 I ended up having to mess around trying to remove the space from the package name before I could get another project to reference it. All I have done is update the packages, and change the call to BasicPublish in RabbitAdvancedBus to remove the immediate flag. So it now calls the overload with 5 params.