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

Updating netcoreapp2.1 dependencies in Microsoft.NET.Test.Sdk.nuspec #2192

Merged
merged 1 commit into from
Sep 24, 2019

Conversation

vagisha-nidhi
Copy link
Contributor

Related issue
#2188

@singhsarab singhsarab merged commit be51dd7 into microsoft:master Sep 24, 2019
@sharwell
Copy link
Member

sharwell commented Jul 29, 2020

This change arbitrarily broke testing against netcoreapp1.1 👎 (this is the TFM we used for testing our netstandard1.x libraries, which remains a supported target despite a new inability to test it)

sharwell added a commit to dotnet/roslyn-sdk that referenced this pull request Jul 29, 2020
Support for netcoreapp1.1 was removed in microsoft/vstest#2067 and
microsoft/vstest#2192, so we can no longer take updates to this package.
dotnet-maestro bot added a commit to dotnet/roslyn-sdk that referenced this pull request Jul 29, 2020
[master] Update dependencies from dotnet/arcade
- Updates:
  - Microsoft.DotNet.Arcade.Sdk: from 5.0.0-beta.20117.3 to 5.0.0-beta.20374.1

 - Upadte xcopy-msbuild

 - Switch to Arcade UnitTest targets and props

 - Install the 3.1.0 runtime for test running

 - Use default test versions from Arcade

 - Work around implicit package reference warning

 - Set DOTNET_ROOT variable

 - Remove not working workaround for implicit package reference

 - Reference the XUnit Assert package

 - Lock to prior version of Microsoft.NET.Test.Sdk

Support for netcoreapp1.1 was removed in microsoft/vstest#2067 and
microsoft/vstest#2192, so we can no longer take updates to this package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants