-
Notifications
You must be signed in to change notification settings - Fork 148
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 dnxcore50 #120
Comments
Weeeell, roadmap at present doesn't include it - but that's very much a case of not having a fully fledged roadmap. If you know what to do - or can point me in the right direction - I'll have a look and see what can be done, I'm assuming it's not working for you, if so - it'd be handy to know what isn't working so I can look more in depth. I'll be frank though - having just run a Portability Report - it looks like it'd be a lot of work to get it in place, and some fairly significant changes - I'm not saying 'no' but just worth bearing it in mind. |
I don't know what specifically needs to be done. I am attempting to analyze the feasibility of porting our solution and started with the third party libraries we reference to see if/when they would support it. |
OK, well - I'll have a shufty and see how feasible it is! |
Thank you Chris. |
Keep in mind the ASP.NET 5 project is still making regular breaking changes on each beta. My Neo4j project is using ASP.NET 5 since Beta4 but targeting dnx451 only precisely due to lack of support in the nuget ecosystem. I suspect it will take some time for everyone to catch up. EDIT: Maybe it isn't so hard after all - by targeting PCL, you get dnx50. I think.... |
@neutmute I am well aware. The reason I am looking into this is we are trying to utilize docker containers, it only runs on Windows Server 2016 and the support is very flimsy at best. To get around this we were hoping to be able to target the core 50 framework so we could deploy to a linux server as the docker support there is much better. |
I'm closing this issue in lieu of #135 targeting .net core... |
What does your roadmap looked like for adding the ability to target .NET Core?
The text was updated successfully, but these errors were encountered: