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

.NET Core November Update - 2.1.14, 2.2.8, and 3.0.1 #3848

Open
jamshedd opened this issue Nov 19, 2019 · 13 comments
Labels

Comments

@jamshedd
Copy link
Member

@jamshedd jamshedd commented Nov 19, 2019

Included fixes address issues detailed in the release notes.

.NET Core

Please report any issues you find with these releases, either responding to this issue, creating a new issue here or creating a new issue in one of the following repos:

.NET Support Policies

Microsoft support policies are defined in the following documents:

@Nothing-Works

This comment has been minimized.

Copy link

@Nothing-Works Nothing-Works commented Nov 19, 2019

Inkedscreenshot-dotnet microsoft com-2019 11 20-09_14_44_LI
according to Vs release notes, I can not see Visual Studio 16.3.11. So is it included in VS or I have to manually download it?

@jamshedd

@vivmishra

This comment has been minimized.

Copy link
Member

@vivmishra vivmishra commented Nov 19, 2019

Sorry, that is a mistake, it is being fixed now. the change will be live in a few mins.

Since, this (non-sec) Core release is out of sync with VS releases, it will go out with the next set of VS releases in future.

@IanKemp

This comment has been minimized.

Copy link

@IanKemp IanKemp commented Nov 20, 2019

2.2.7 contained SDK 2.2.402 for VS 2019 v16.2, but this release has no SDK for 16.2 only for 16.0. Does that mean SDK 2.2.402 is the latest and that if we already have it, we don't need SDK 2.2.207 from 2.2.8?

@corne-w

This comment has been minimized.

Copy link

@corne-w corne-w commented Nov 20, 2019

2.2.7 contained SDK 2.2.402 for VS 2019 v16.2, but this release has no SDK for 16.2 only for 16.0. Does that mean SDK 2.2.402 is the latest and that if we already have it, we don't need SDK 2.2.207 from 2.2.8?

Wondering this as well. The same goes for 2.1.14 which contains SDK 2.1.607 whereas 2.1.13 contains SDK 2.1.802.

@vivmishra

This comment has been minimized.

Copy link
Member

@vivmishra vivmishra commented Nov 20, 2019

@Angr1st

This comment has been minimized.

Copy link

@Angr1st Angr1st commented Nov 24, 2019

This now supports F# 4.6 instead of F# 4.7 like the 3.0.100 SDK? May I ask why this is rolled back a minor version?

@vivmishra

This comment has been minimized.

Copy link
Member

@vivmishra vivmishra commented Nov 26, 2019

@AngelosP, F# version issue should be fixed now, thanks for reporting.
https://dotnet.microsoft.com/download/dotnet-core/3.0

@madhon

This comment has been minimized.

Copy link

@madhon madhon commented Nov 27, 2019

@vivmishra what about all the messed up 2,2 SDK versions

@madhon

This comment has been minimized.

Copy link

@madhon madhon commented Dec 3, 2019

@jamshedd what about all the messed up 2,2 SDK versions

@jamshedd

This comment has been minimized.

Copy link
Member Author

@jamshedd jamshedd commented Dec 3, 2019

2.2.7 contained SDK 2.2.402 for VS 2019 v16.2, but this release has no SDK for 16.2 only for 16.0. Does that mean SDK 2.2.402 is the latest and that if we already have it, we don't need SDK 2.2.207 from 2.2.8?

Wondering this as well. The same goes for 2.1.14 which contains SDK 2.1.607 whereas 2.1.13 contains SDK 2.1.802.

This is expected - .NET Core SDK versions are supported based on the Visual Studio lifecycle. The Visual Studio version (16.2) that includes the 2.1.802 SDK went out of support when VS 16.3 shipped, so we did not ship the corresponding Core SDK.

@vivmishra, can you please confirm the version numbers I quoted are right?

@vivmishra

This comment has been minimized.

Copy link
Member

@vivmishra vivmishra commented Dec 3, 2019

Yes, the versions are right. 2.1.802/2.2.402 shipped with VS 16.2 that went out of support when VS 16.3 went live. We understand that is confusing for people - we are working on a response for this.

@madhon

This comment has been minimized.

Copy link

@madhon madhon commented Dec 4, 2019

2.2.7 contained SDK 2.2.402 for VS 2019 v16.2, but this release has no SDK for 16.2 only for 16.0. Does that mean SDK 2.2.402 is the latest and that if we already have it, we don't need SDK 2.2.207 from 2.2.8?

Wondering this as well. The same goes for 2.1.14 which contains SDK 2.1.607 whereas 2.1.13 contains SDK 2.1.802.

This is expected - .NET Core SDK versions are supported based on the Visual Studio lifecycle. The Visual Studio version (16.2) that includes the 2.1.802 SDK went out of support when VS 16.3 shipped, so we did not ship the corresponding Core SDK.

@vivmishra, can you please confirm the version numbers I quoted are right?

@jamshedd & @vivmishra so based on that which is what is the correct sdk to install for VS 2019 v16.3 or v16.4 ? as you dont really answer that question.

@vivmishra

This comment has been minimized.

Copy link
Member

@vivmishra vivmishra commented Dec 4, 2019

@madhon , there is no update for v16.3 as this out of band (non-sec) .NET Core release did not align with any planned v16.3 release. v16.3 is now currently out of support as v16.4 went live on 12/3. Of course, you can still install any of the 2.X or 3.0 package (as per your need) from this release on v16.3, but, you should ideally upgrade to v16.4 as that is the officially supported version.

v16.4 already includes what we have to offer from this release (2.1.14, 2.2.8, 3.0.1) plus 3.1 SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.