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

Target .NET Standard 2.0 again #1081

Closed
KexyBiscuit opened this issue Oct 18, 2019 · 1 comment · Fixed by #1105
Closed

Target .NET Standard 2.0 again #1081

KexyBiscuit opened this issue Oct 18, 2019 · 1 comment · Fixed by #1105
Labels
enhancement New feature or request
Milestone

Comments

@KexyBiscuit
Copy link
Contributor

EF Core 3.1 retargets .NET Standard 2.0. Will efcore.pg target .NET Standard 2.0 again before EF Core 5(?) releases to satisfy UWP and .NET Framework requirements?

@roji
Copy link
Member

roji commented Oct 18, 2019

Absolutely, the Npgsql provider will target whatever EF Core itself will target. Will use this issue to track.

@roji roji added the enhancement New feature or request label Oct 18, 2019
@roji roji changed the title Will efcore.pg target .NET Standard 2.0 again? Target .NET Standard 2.0 again Oct 18, 2019
@roji roji added this to the 3.1.0 milestone Oct 18, 2019
roji added a commit that referenced this issue Oct 31, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Oct 31, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Oct 31, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Oct 31, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Oct 31, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 1, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
roji added a commit that referenced this issue Nov 3, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
@roji roji closed this as completed in #1105 Nov 3, 2019
roji added a commit that referenced this issue Nov 3, 2019
* Remove unneeded RemoveConvert in JSON POCO translator as it has been
  obsoleted upstream. It wasn't actually necessary anyway.
* Target .NET Standard 2.0
* Various test fixes for 3.1
* Correct all test issues flagged by xunit analyzer

Closes #1081
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants