-
Notifications
You must be signed in to change notification settings - Fork 223
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
Labels
enhancement
New feature or request
Milestone
Comments
Absolutely, the Npgsql provider will target whatever EF Core itself will target. Will use this issue to track. |
roji
changed the title
Will efcore.pg target .NET Standard 2.0 again?
Target .NET Standard 2.0 again
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
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
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?
The text was updated successfully, but these errors were encountered: