We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/16.3.0 lists netcoreapp1.0 as a target, but the dependency Microsoft.TestPlatform.TestHost 16.3.0 has netcoreapp2.1 as the lowest netcore target.
netcoreapp1.0
Microsoft.TestPlatform.TestHost 16.3.0
netcoreapp2.1
This seems due to a mismatch between https://github.com/microsoft/vstest/blob/master/src/package/nuspec/Microsoft.NET.Test.Sdk.nuspec and https://github.com/microsoft/vstest/blob/master/src/package/package/package.csproj (and maybe more places?)
NuGet should list the same target frameworks as the csproj
NuGet lists netcoreapp1.0, which the csproj does not.
#2067 replaced the netcoreapp1.0 with netcoreapp2.1. Could it just add the newer target framework instead of replacing the old?
The text was updated successfully, but these errors were encountered:
vagisha-nidhi
No branches or pull requests
Description
https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/16.3.0
lists
netcoreapp1.0
as a target, but the dependencyMicrosoft.TestPlatform.TestHost 16.3.0
hasnetcoreapp2.1
as the lowest netcore target.This seems due to a mismatch between https://github.com/microsoft/vstest/blob/master/src/package/nuspec/Microsoft.NET.Test.Sdk.nuspec
and
https://github.com/microsoft/vstest/blob/master/src/package/package/package.csproj
(and maybe more places?)
Expected behavior
NuGet should list the same target frameworks as the csproj
Actual behavior
NuGet lists netcoreapp1.0, which the csproj does not.
Other
#2067 replaced the
netcoreapp1.0
withnetcoreapp2.1
.Could it just add the newer target framework instead of replacing the old?
The text was updated successfully, but these errors were encountered: