.NET Core 2.1.6

[leecow]

November 2018 .NET Updates

The following .NET updates were released in November 2018. This issue will be updated if there are any additional releases during the month.

.NET Core

• .NET Core November 2018 (2.1.6 and SDK 2.1.500) Update release notes

A discussion issue is available for questions or feedback about this release.

.NET Support Policies

Microsoft support policies are defined in the following documents:

• Microsoft .NET Support Policy
• .NET Core OS Lifecycle Policy

Previous Updates

• October 2018
• September 2018
• August 2018
• July 2018
• June 2018
• May 2018

[yaakov-h]

@leecow the October link is broken in the related Announcements issue.

[karelz]

@yaakov-h thanks! Fixed.

[jarz]

I'm unable to restore an internal NuGet package from Azure DevOps Artifacts with SDK 2.1.500, but SDK 2.1.403 works. Should I create an issue here or in another repo?

[karelz]

@jarz it does not seem to be related to 2.1.6, so not on this issue.
Try to narrow down what triggers the problem - is it your environment? (Azure DevOps Artifacts - whatever that is) Or is it reproducible under some circumstances everywhere? If it is not specific problem of the environment, then this repo is a good start.

[megafinz]

Seems like after update to 2.1.6 our CI silently stopped running unit tests with the following message:

Skipping running test for project <ProjectPathAndName>. To run tests with dotnet test add "<IsTestProject>true<IsTestProject>" property to project file.

CI pulled the following docker image when tests stopped working (it was on November 13th):

Pulling docker image microsoft/dotnet:2.1-sdk ...
Using docker image sha256:732ac6c02e837b14d3ff36f5b2e3d732a7a52c029e489e1ba905996ddf05f358 for microsoft/dotnet:2.1-sdk ...

Previous image doesn't seem to have this behavior, tests worked fine:

Using docker image sha256:6baac5bd0ea2ec449a4643e27d701ce06f8d2b2bc2b150a425c59015e5204dc3 for microsoft/dotnet:2.1-sdk ...

[karelz]

@megafinz is that output from msbuild? Are you able to track down what triggers it?
@nguerrera @dsplaisted can you please help route it?

[dsplaisted]

@megafinz Can you file an issue in https://github.com/microsoft/vstest with as much information as possible?

[joeaudette]

fyi, broken link for release notes here: https://www.microsoft.com/net/download

[karelz]

@joeaudette thanks! I merged your report with #2062 (same problem on another subpage)

[megafinz]

@karelz @dsplaisted I was trying to find a repro but had no luck. I believe new version of SDK ignores unit test project that have no IsTestProject property set to true. This property is set either explicitly in project file or by referencing Microsoft.NET.Test.Sdk package (which we do reference actually). I discovered that if this package is not present on disk when tests are run, then the aforementioned message appears and tests are skipped. So I believe our problem is caused by some issue with our CI, which was masked by previous SDK still running tests in projects that are not actually marked by IsTestProject.

[leecow]

Closing older release. If there are pending discussions, please keep them going in the 2.1.7 issue