Skip to content

Conversation

@ViktorHofer
Copy link
Member

CoreLib analyzers were unintentionally disabled with
6afe96c. This re-enables the analyzers
and conditions one which brings in external dependencies that CoreLib
can't deal with.

Fixes #422

CoreLib analyzers were unintentionally disabled with
6afe96c. This re-enables the analyzers
and conditions one which brings in external dependencies that CoreLib
can't deal with.
@ViktorHofer
Copy link
Member Author

I'll remove that package as its description clearly state that it shouldn't be referenced directly. @safern do you have context why that package was referenced directly in corefx/arcade?

Microsoft.CodeAnalysis.Common shouldn't be referenced directly,
therefore removing that package from the common location and only
restoring and marking it as an analyzer in the libraries restore phase.
@ViktorHofer
Copy link
Member Author

OK, so the transitive dependency to Microsoft.CodeAnalysis.Common is required becaues of the special way we add analyzers to projects in libraries. We will clean this up with @Anipik's work to enable project restore for non test projects in libraries.

@ViktorHofer
Copy link
Member Author

This should be ready, can someone pls approve? Thanks

@ViktorHofer
Copy link
Member Author

Thanks, merging as the previous run was green (except an unrelated test failure) and I just changed a comment which re-triggered CI.

@ViktorHofer ViktorHofer merged commit f84d01b into dotnet:master Dec 2, 2019
@ViktorHofer ViktorHofer deleted the EnableCoreLibAnalyzers branch December 2, 2019 17:13
Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

safern pushed a commit that referenced this pull request Dec 3, 2019
* Re-enable CoreLib analyzers

CoreLib analyzers were unintentionally disabled with
6afe96c. This re-enables the analyzers.

* Remove Microsoft.CodeAnalysis.Common from common

Microsoft.CodeAnalysis.Common shouldn't be referenced directly,
therefore removing that package from the common location and only
restoring and marking it as an analyzer in the libraries restore phase.
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Re-enable analyzers for System.Private.CoreLib

4 participants