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

Upgrading project to remove EOL frameworks #143

Closed
wants to merge 2 commits into from
Closed

Upgrading project to remove EOL frameworks #143

wants to merge 2 commits into from

Conversation

ewassef
Copy link

@ewassef ewassef commented Feb 18, 2020

Updating the application to .net core 3.1 based on the guidelines defined here

This updates the libraries to .netstandard 2.1 but maintains .netstandard 2.0 for those using this library with .netcoreapp 2.1

this will also rev the version from 1.0.1 to 1.0.2 to indicate a patch increment (even though the framework was updated) as the package is still backwards compatible and no new features have been added

@ewassef ewassef requested a review from abergs February 18, 2020 22:36
@ewassef
Copy link
Author

ewassef commented Feb 18, 2020

@abergs The pipeline step that's breaking is explicitly trying to build in .netcore framework 2.2 (this will always break since this PR is removing that).
Is there a particular reason the framework was specified?

@abergs
Copy link
Collaborator

abergs commented Mar 2, 2020

@ewassef The pipeline configuration needs a version of the SDK specified, however as discussed in #124 and #126 that is due to change soon.

I need to review these changes compared those made by @Shtong in #124 and evaluate which of these PRs we should use since I believe they are conflicting atm.

@ewassef
Copy link
Author

ewassef commented Mar 16, 2020

That makes a ton of sense. Do you know when something like this will happen? We are wanting to start using this in .net 3.1 as soon as we can

@ewassef
Copy link
Author

ewassef commented Mar 22, 2020

What would you recommend in regards to the timeline? Should we fork and attempt a merge in the future?

@abergs
Copy link
Collaborator

abergs commented Mar 24, 2020

Done in #145.

Are there any other changes you want to make?

@abergs abergs closed this Mar 24, 2020
@ewassef
Copy link
Author

ewassef commented Mar 24, 2020

Nope! thank you for doing this. I will try to pull the latest and incorporate them in. If I run into anything else, ill submit a fix!

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

Successfully merging this pull request may close these issues.

None yet

2 participants