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

Move warning into a target to fix msbuild error #1856

Merged
merged 1 commit into from
Dec 4, 2018

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Dec 4, 2018

Fixes msbuild error The <Warning> tag is no longer supported as a child of the <Project> element.

Currently the Microsoft.Net.Test.Sdk nuget package can't be used with new msbuild versions as it throws if a Warning tag appears as a child of the Project element.. Found a related issue that talks about the change: dotnet/msbuild#3858. This issue already existed before my recent changes.

As the current package (https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/16.0.0-preview-20181128-01) is broken can we please publish a new one asap?

cc @singhsarab @mayankbansal018 @karanjitsingh

Fixes msbuild error "The <Warning> tag is no longer supported as a
child of the <Project> element".
@singhsarab singhsarab merged commit 069c5f8 into microsoft:master Dec 4, 2018
@singhsarab
Copy link
Contributor

@ViktorHofer Can you please test with the latest pre-release package from myget feed: https://dotnet.myget.org/F/vstest/api/v3/index.json

@ViktorHofer ViktorHofer deleted the FixWarningTestSdkTargets branch December 4, 2018 14:44
@ViktorHofer
Copy link
Member Author

Sure but the latest pre-release package does not contain my changes: 16.0.0-preview-20181204-02

@singhsarab
Copy link
Contributor

It's 16.0.0-preview-20181204-03 that should have it.

@ViktorHofer
Copy link
Member Author

Thanks. It works as expected, just tried it out in CI and locally.

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