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 2.1 Preview 1 #1297

Closed
leecow opened this Issue Feb 27, 2018 · 18 comments

Comments

Projects
None yet
@leecow
Member

leecow commented Feb 27, 2018

.NET Core 2.1 Preview 1

.NET Core Preview 1 is available. This release includes:

  • .NET Core 2.1.0-preview1-26216-03 and .NET Core SDK 2.1.300-preview1-008174

You can read about the updates in the .NET Core blog post

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

@leecow leecow added the Announcement label Feb 28, 2018

@leedale1981

This comment has been minimized.

leedale1981 commented Mar 1, 2018

Probably a stupid question but why does .NET Core 2.1.0-preview1 install SDK 2.1.300 but the previous version 2.0.5 installs a later version of the SDK 2.1.4?

@Petermarcu

This comment has been minimized.

Member

Petermarcu commented Mar 1, 2018

Because versioning got out of sync and confused people. We now plan to always alight the major and minor.

@savornicesei

This comment has been minimized.

savornicesei commented Mar 1, 2018

Please, please, please, have an unstable and a stable repo for linux distribution.
It took me some time to get everything right on my openSUSE box and I don't want any updates to preview versions of .NET

Other than that ... long live .NET on linux! 👍

@leecow

This comment has been minimized.

Member

leecow commented Mar 1, 2018

Thanks @savornicesei - I'm looking into our options.

@savornicesei

This comment has been minimized.

savornicesei commented Mar 2, 2018

@leecow Perhaps open build system could ease the pain of linux multi-distro preview/stable releases

@tkggusraqk

This comment has been minimized.

tkggusraqk commented Mar 3, 2018

TransactionScope, is the problem fixed?

@EdLorenzQAT

This comment has been minimized.

EdLorenzQAT commented Mar 3, 2018

I tested TransactionScope on Linux using this preview and it takes a NPE which is the same result I was seeing from the previous version.
However, under windows, initial testing looks good.

@jherby2k

This comment has been minimized.

jherby2k commented Mar 7, 2018

I'd like to try the new Span-ified functionality like Stream.Read(Span destination) in my library projects, but it looks like they will need to target .NET Standard 2.1. Is there even going to be a .net standard 2.1?? Any other way to obtain these APIs? I added System.Memory but it looks like this method is part of the SDK.

@BennyTordrupVisma

This comment has been minimized.

BennyTordrupVisma commented Mar 8, 2018

LiuHai119, please stop spamming.

@simeyla

This comment has been minimized.

simeyla commented Mar 8, 2018

Is there a target date for Preview 2?

@DaveSlinn

This comment has been minimized.

DaveSlinn commented Mar 12, 2018

The recent update of VS 2017 to 15.6 has broken the build of our solution. It seems to have installed a new folder in the dotnet/sdk called 2.1.100 - and the dotnet cli seems to no longer resolve the references in our solution file properly.
image
When I do a dotnet --version, I get 2.1.100. Dev boxes that have are still on 1.5.5.7 do not have 2.1.100 (they have 2.1.4) and still work fine.

What is 2.1.100 and what changed in it from 2.1.4 that is now breaking our builds?

@Petermarcu

This comment has been minimized.

Member

Petermarcu commented Mar 14, 2018

@livarcocc Can you look into this one?

@DaveSlinn

This comment has been minimized.

DaveSlinn commented Mar 14, 2018

Update: after I posted this, I looked into it further and discovered that the dotnet restore was now stopping our builds (whereas prior to the update, it would just display an MSB4019 error. @livarcocc has already redirected my issue on that to the NuGet team for input at NuGet/Home#6665

@bobuva

This comment has been minimized.

bobuva commented Mar 19, 2018

I've installed the preview and trying to make an SSL connection that requires Tls1.2 and ALPN. I know I'm using TLS1.2 because I specify it here:

                    ProxyClient.TestUbuntuHost,
                    null,
                    System.Security.Authentication.SslProtocols.Tls12,
                    false);

but how do I know whether it is using ALPN in the handshake?

Note: I'm going to create a separate issue to get clarification on ALPN usage.

@Petermarcu

This comment has been minimized.

Member

Petermarcu commented Apr 5, 2018

@karelz should we open an issue in corefx to track @bobuva's reported issue?

@karelz

This comment has been minimized.

Member

karelz commented Apr 5, 2018

Sure, filing questions as separate issues is a good idea. CoreFX is a good place to ask this one.
ALPN is going to be used only if you try to negotiate some application protocol via ApplicationProtocols. See a test. You can always verify by capturing networking traffic via Wireshark.

@buvinghausen

This comment has been minimized.

buvinghausen commented Apr 10, 2018

Was excited to see .NET Core 2.1 Preview 2 drop on NuGet 16 hours ago. Is there an ETA on when the runtime & SDK will make it to Docker Hub?

@Petermarcu

This comment has been minimized.

Member

Petermarcu commented Apr 11, 2018

Closing this issue in favor of Preview 2. #1422

@Petermarcu Petermarcu closed this Apr 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment