You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on an .NET Core REST API project and we need to integrate a RabbitMQ client for bus messaging. I've tried to add the RawRabbit vNext package from nuget add it crashes, saying that there is no support for DNX Core 5.0
See the attached picture
So for the moment RawRabbit vNext doesn't work for .Net Core (DNX Core 5.0) ?
PS: I saw that there is a issue reported by you on RabbitMQ Client and you say that after it is closed we will have RawRabbit vNext running on .NET Core, correct?
As far as I google it to get some info for the moment there is no RabbitMQ client running for .Net Core (DNX Core 5.0) ?
Thanks in advance for your answers
The text was updated successfully, but these errors were encountered:
viorelabrudan
changed the title
Hi,
Does RawRabbit runs on DNX Core 5.0 (.Net Core) ?
May 8, 2016
Hi @viorelabrudan, thanks for reporting this. The short answer is: no, not at the moment. The main reason is that RawRabbit is dependent on the underlying (official) RabbitMQ.Client, which does not support .NET Core. As soon as it does, we'll have support within hours ;)
You can read more about this in #56, where options are proposed, too.
We are working on an .NET Core REST API project and we need to integrate a RabbitMQ client for bus messaging. I've tried to add the RawRabbit vNext package from nuget add it crashes, saying that there is no support for DNX Core 5.0
See the attached picture
So for the moment RawRabbit vNext doesn't work for .Net Core (DNX Core 5.0) ?
PS: I saw that there is a issue reported by you on RabbitMQ Client and you say that after it is closed we will have RawRabbit vNext running on .NET Core, correct?
As far as I google it to get some info for the moment there is no RabbitMQ client running for .Net Core (DNX Core 5.0) ?
Thanks in advance for your answers
The text was updated successfully, but these errors were encountered: