-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Update SDK #49297
Update SDK #49297
Conversation
Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at. |
This error in Update: it looks like it is feasible by passing the cc: @RussKie @joperezr Do we expect a more permanent diagnostic ID to land soon for this? Also, is suppressing the diagnostic in test code is the right approach? |
d667e15
to
c30eaf5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't want to overwrite existing NoWarn
Co-authored-by: William Godbe <[email protected]>
Yes, it should be safe to suppress. This is still WIP (dotnet/extensions#4161). Eventually, there will be IDs defined. /cc: @geeknoid |
* Update global.json As per dotnet/aspnetcore#49297 * Update Directory.Build.targets Suppress TBD * Fix build
No description provided.