Skip to content

Fix SuppressTrimAnalysisWarnings#17050

Merged
sbomer merged 2 commits intodotnet:mainfrom
sbomer:fixSuppressTrimAnalysisWarnings
Apr 21, 2021
Merged

Fix SuppressTrimAnalysisWarnings#17050
sbomer merged 2 commits intodotnet:mainfrom
sbomer:fixSuppressTrimAnalysisWarnings

Conversation

@sbomer
Copy link
Copy Markdown
Member

@sbomer sbomer commented Apr 20, 2021

This needs to be set before the .NET SDK targets get imported, otherwise the .NET defaults win.

I was too hasty in #16865, and regressed this when I responded to @eerhardt's feedback. @pranavkm noticed that blazor was producing warnings after my change. I've now double-checked that this change doesn't produce warnings by default for blazor/web.

This needs to be set before the .NET SDK targets get imported, otherwise
the .NET defaults win.
@ghost
Copy link
Copy Markdown

ghost commented Apr 20, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@eerhardt
Copy link
Copy Markdown
Member

Can we add a test to ensure it doesn't regress again?

@pranavkm
Copy link
Copy Markdown
Contributor

https://github.com/dotnet/sdk/blob/main/src/Tests/Microsoft.NET.Sdk.BlazorWebAssembly.Tests/WasmPublishTest.cs#L37 would be a good place to add one.

@sbomer sbomer requested a review from agocke April 20, 2021 22:08
@sbomer sbomer merged commit 23e7fd3 into dotnet:main Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants