- Notifications
You must be signed in to change notification settings - Fork135
Move to new SDK for .Net Standard Support#92
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
rolfwessels commentedNov 4, 2017
Any progress on this ? |
@rolfwessels kind of forgot about this. 😹 I believe the core project move to .NetStandard has been complete. It should just work right now. I wouldn't mind some testing or some input from any contributors. |
rolfwessels commentedNov 7, 2017
Cool, I'm porting a mono app over to .netcore (its been a bit tedious) as soon as I have it actually running again on .net core I will let you know. Thanks :-) |
hugener commentedDec 1, 2017
Any news on this? |
@hugener I'm apparently easily distracted as I keep on forgetting about this.And I just had a long boring plane ride where I could have completed this... At this point everything in the nuget package has been moved over, IIRC and this pull request can be merged at anytime. The work on moving the other projects can be completed anytime in the future. |
Uh oh!
There was an error while loading.Please reload this page.
I propose a three stage migration:
Looking over the projects briefly, this should be a drop in replacement, hopefully.