Skip to content
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

Any plans to supports .NET Core? #581

Closed
g0194776 opened this issue Jun 14, 2016 · 10 comments
Closed

Any plans to supports .NET Core? #581

g0194776 opened this issue Jun 14, 2016 · 10 comments

Comments

@g0194776
Copy link

g0194776 commented Jun 14, 2016

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

@zidad
Copy link
Member

zidad commented Jun 14, 2016

Hi, I don't think it's planned at the moment, but most likely after the RTM (but PR's welcome of course :)). The RabbitMQ.Client only started to support it yesterday: rabbitmq/rabbitmq-dotnet-client#148

@g0194776
Copy link
Author

@zidad

Thank you.

@radicalgeek
Copy link
Contributor

radicalgeek commented 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, rabbitmq/rabbitmq-dotnet-client#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.

@zidad
Copy link
Member

zidad commented Jul 4, 2016

@radicalgeek Great thanks a lot! Is there anything I can do?

@radicalgeek
Copy link
Contributor

ummmm....Other than put serialisable support back into netcore!

No, it's not going bad, I only have 12 errors left. With a bit of hacking it won't be hard to make it work, getting it into any kind of state worthy of a pull request is another matter.

@zidad
Copy link
Member

zidad commented Jul 4, 2016

@radicalgeek You mean the [Serializable] attribute? I don't think it's required/being used, and if it is, it probably shouldn't!

I would vote for removing it from the code base completely. @micdenny @Pliner agree?

@micdenny
Copy link
Member

micdenny commented Jul 4, 2016

The attribute Serializable is in netcore: https://github.com/dotnet/corefx/blob/53204dc13d67e8266a0e9b88845d13220a69afda/src/System.Runtime.Serialization.Formatters/src/System/SerializableAttribute.cs

I don't know why was used, probably is not need it as @zidad suggested.

@zidad
Copy link
Member

zidad commented Jul 4, 2016

Here's a PR for removing [Serializable] #587

@radicalgeek
Copy link
Contributor

radicalgeek commented Jul 4, 2016

@micdenny I read this regarding Serializable https://github.com/dotnet/corefx/issues/6564

I have 4 weird errors left, telling me that BasicPublish dosn't take 6 params. It clearly dose, and the editor is not giving me the error, only the compiler. Pretty close though. It works when I edit to call the overload that doesn't take the immediate flag.

@radicalgeek
Copy link
Contributor

radicalgeek commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants