-
Notifications
You must be signed in to change notification settings - Fork 311
Remove support for .NET Standard 2.0 and 2.1 #2386
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
Conversation
src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SNI/SNICommon.cs
Outdated
Show resolved
Hide resolved
src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SNI/SNIProxy.cs
Outdated
Show resolved
Hide resolved
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2386 +/- ##
==========================================
- Coverage 72.69% 71.05% -1.64%
==========================================
Files 313 296 -17
Lines 61737 60725 -1012
==========================================
- Hits 44878 43150 -1728
- Misses 16859 17575 +716
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@JRahnama All net462 builds pass, despite being labelled with netstandard2.1 - but maybe the label is misleading? |
labels are misleading, I will try to make a test pipeline for this PR today. Update: failures are all due to building netstandard tests which are expected. |
@JRahnama any progress on the pipeline Update? |
@David-Engel @JRahnama Is this still on the radar? |
A new file with .NET Standard support has been added in pull request #2310. |
I will merge with latest main and remove it. |
How is it going with the pipeline update?? |
We're going to set up a test pipeline to verify the outcome of this change. Once it's merged, we'll replace it with the current CI. |
@DavoudEshtehari sounds great. I will Update tomorrow |
You should be able to see this pipeline, which has been setup for your branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! In addition to the CI pipeline, we recently pushed a few YAML files for production pipeline into the GitHub repo, and they should be updated and verified internally. We'll prepare the necessary internal changes to ensure that these PRs are merged with the least time gap.
@DavoudEshtehari Thanks, let me know if there is anything else I need to do |
fix bad merge
fixes #2340