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.

Sign up for GitHub

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

Jump to bottom

Should we still run Microsoft.DotNet.CodeAnalysis for libraries? #34407

Closed
ViktorHofer opened this issue Apr 1, 2020 · 2 comments
Closed

Should we still run Microsoft.DotNet.CodeAnalysis for libraries? #34407

ViktorHofer opened this issue Apr 1, 2020 · 2 comments
Labels
area-Infrastructure-libraries untriaged New issue has not been triaged by the area owner

Comments

@ViktorHofer
Copy link
Member

from @ericstj in #33553 (comment):

Do we even care about this analyzer any more? It was particularly helpful when porting code that was designed for desktop and making it work for AppX, but I wonder if its even relevant (especially since we just baseline all the failures).

cc @safern @Anipik @joperezr
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Infrastructure-libraries untriaged New issue has not been triaged by the area owner labels Apr 1, 2020
@ViktorHofer ViktorHofer mentioned this issue Apr 1, 2020
Merged
@stephentoub
Copy link
Member

#33867

@ViktorHofer
Copy link
Member Author

Thanks, closing as duplicate.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Infrastructure-libraries untriaged New issue has not been triaged by the area owner
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stephentoub @ViktorHofer @Dotnet-GitSync-Bot