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

Migrate To Dotnet Core #51

Open
ritasker opened this issue Feb 27, 2017 · 2 comments
Open

Migrate To Dotnet Core #51

ritasker opened this issue Feb 27, 2017 · 2 comments

Comments

@ritasker
Copy link

Hi,

I am just wondering if you have a plan to migrate to dotnet core.
I have a dnc project that uses signalr, and I need to introduce a backplane so I can scale out the application. I am already using rabbitmq so this package seems a good choice.

@mdevilliers
Copy link
Owner

mdevilliers commented Feb 27, 2017

Hey Richard,

I don't have any plans to migrate to dotnet core [1] but would gladly take a contribution ;-)

What sort of effort would it take to make the transition? I would assume very little as to be honest there isn't much code in this repo with about 50% of the logic in the RMQ plugin.

[1] I essentially do next to 0% .net development at the moment and would struggle to fit it in with my current free bandwidth. My free time devoted to this project is essentially looking after the issues, reviewing PRs and doing the releases.

@ritasker
Copy link
Author

Hey Mark,

I don't think there will be a massive transition, the RabbitMQ.Client lib is already on dotnet core, the biggest change I see is moving to the new DI model in ASPNET Core and updating the project files.

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

No branches or pull requests

2 participants