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

Remove netstandard1.3 from code base #59177

Merged
merged 6 commits into from
Feb 7, 2022
Merged

Remove netstandard1.3 from code base #59177

merged 6 commits into from
Feb 7, 2022

Conversation

jaredpar
Copy link
Member

@jaredpar jaredpar commented Jan 31, 2022

The remote debugger components moved to their minimum framework install
to 4.6.2 where it was previously 2.0. That means we can remove the uses
of netstandard1.3 in our code base as they existed just to support
this specific case.

This means we can also remove our use of net2.0 in the code base and
replace it with net462. That is a more involved changed though and
going to take that a piece at a time. Removing netstandard1.3 is an
important step because presently it's blocking us from updating to the
latest System.Collections.Immutable as it dropped support for
netstandard1.3

The remote debugger components moved to their minimum framework install
to 4.6.2 where it was previously 2.0. That means we can remove the uses
of `netstandard1.3` in our code base as they existed just to support
this specific case.

This means we can also remove our use of `net2.0` in the code base and
replace it with `net462`. That is a more involved changed though and
going to take that a piece at a time. Removing `netstandard1.3` is an
important step because presently it's blocking us from updating to the
latest System.Collections.Immutable as it dropped support for
`netstandard1.3`
@jaredpar
Copy link
Member Author

@dotnet/roslyn-infrastructure, @tmat PTAL

@JoeRobich
Copy link
Member

Test insertion - https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/376937 (microsoft)

Copy link
Contributor

@RikkiGibson RikkiGibson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensuring we don't merge until we have a passing VS test insertion.

@jaredpar
Copy link
Member Author

jaredpar commented Feb 2, 2022

@RikkiGibson verified offline with @333fred that the VS test run didn't reveal any issues hence think you are safe to remove your "request changes" now. If there are other checks you think we should run please let me know.

@RikkiGibson RikkiGibson dismissed their stale review February 2, 2022 22:34

I don't object to merging, though my preference would be to wait for after the 17.2-p1 snap (mid-day tomorrow).

@jaredpar
Copy link
Member Author

jaredpar commented Feb 3, 2022

@dotnet/roslyn-infrastructure, @dotnet/roslyn-ide can i get a second review here? This is impacting the ability for VS Plat to upgrade S.C.I

Copy link
Member

@333fred 333fred left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we snapped for 17.2p2 at this point @RikkiGibson?

@RikkiGibson
Copy link
Contributor

I believe we snapped for 17.2p2 at this point

We hadn't at the time of this comment, but now we have.

@RikkiGibson
Copy link
Contributor

Merge at will :)

@jaredpar jaredpar merged commit b8d2e61 into dotnet:main Feb 7, 2022
@ghost ghost added this to the Next milestone Feb 7, 2022
@jaredpar
Copy link
Member Author

jaredpar commented Feb 7, 2022

Let's see how this goes ...

@RikkiGibson RikkiGibson modified the milestones: Next, 17.2.P2 Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants