-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for DNX Core 5.0 #56
Comments
@sgeef Yes there are. At the moment we are limited by the fact that the official In fact, as soon as the underlying client has support for dnx core, all we have to do is add a single line of code in the |
👍 |
Is there already more news when this is going to ship to RawRabbit? We are starting up a project in .NET Core 5.0 and we need this to make it work on non-windows OS... |
@robvanpamel There are some unofficial ports to support dotnet core out there, but it does not make sense for RawRabbit to rely on them as they are (AFAIK) poorly tested and not production code. Besides, the RabbitMQ team has announced that they will do a complete re-write of their client for dotnet core. There are no easy ways to get any .NET client to run on dotnet core at the moment. What you could do is fork RawRabbit, pick one of the unofficial ports for RabbitMQ.Client, build it and use those binaries in your clone of RawRabbit. You can still leverage the vNext extensions for RawRabbit with DI, Logging and configuration etc. Then, at a later point when the official client supports dotnet core, RawRabbit will be released with a version that supports that, too and you can replace the temporary build of RawRabbit with the official one. I will try to hold the public APIs of RawRabbit intact when the official clients supports dotnet, but if they radically change their API that might reflect in changes in RawRabbit's API, too. Hope this helps! |
Great news, the latest release of For installing though NuGet, use the following command
|
Are there any thoughts about supporting DNX core 5.0?
The text was updated successfully, but these errors were encountered: