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

Enable FxCop Analyzers for the repo #23709

Merged
merged 2 commits into from
Jul 8, 2020
Merged

Conversation

Pilchie
Copy link
Member

@Pilchie Pilchie commented Jul 6, 2020

All rules are currently disabled, except for one that I enabled for
src/Http via a new ".editorconfig" file I added there.

Other changes:

  • Allow editorconfigs in MVC and Razor to flow to the root
  • Consolidate a few editorconfig settings
  • Tweak Ruleset config in Azure/AzureAD where it clashed.

Addresses the beginning of #9620, but it's a fair chunk of work to
enable most rules through the whole repo. That can be done directory by
directory and rule by rule by dropping .editorconfig files though.

Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

Hopefully just needs the $(DotNetBuildFromSource) check.

All rules are currently disabled, except for one that I enabled for
src/Http via a new ".editorconfig" file I added there.

Other changes:

* Allow editorconfigs in MVC and Razor to flow to the root
* Consolidate a few editorconfig settings
* Tweak Ruleset config in Azure/AzureAD where it clashed.

Addresses the beginning of dotnet#9620, but it's a fair chunk of work to
enable most rules through the whole repo. That can be done directory by
directory and rule by rule by dropping .editorconfig files though.
@Pilchie
Copy link
Member Author

Pilchie commented Jul 6, 2020

@javiercn - I'll leave this in case anyone wants to discuss in the @dotnet/aspdoi meeting tomorrow (though I won't be there).

@javiercn
Copy link
Member

javiercn commented Jul 7, 2020

LGTM, I'll make sure we discuss it on Today's meeting, but it sounds reasonable to me. This is a good starting point and we can work on adding rules on a per-case basis as we deem fit.

@javiercn
Copy link
Member

javiercn commented Jul 7, 2020

We didn't get time to discuss this in today's meeting, but I think we can go ahead with these changes and start looking at individual rules.

@mkArtakMSFT mkArtakMSFT added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jul 8, 2020
@Pilchie Pilchie merged commit 1da13e6 into dotnet:master Jul 8, 2020
@Pilchie Pilchie deleted the FxCopAnalyzers branch September 2, 2020 20:15
dougbu pushed a commit to dougbu/razor-compiler that referenced this pull request Nov 17, 2021
All rules are currently disabled, except for one that I enabled for
src/Http via a new ".editorconfig" file I added there.

Other changes:

* Allow editorconfigs in MVC and Razor to flow to the root
* Consolidate a few editorconfig settings
* Tweak Ruleset config in Azure/AzureAD where it clashed.

Addresses the beginning of dotnet/aspnetcore#9620, but it's a fair chunk of work to
enable most rules through the whole repo. That can be done directory by
directory and rule by rule by dropping .editorconfig files though.

Commit migrated from dotnet/aspnetcore@1da13e65017c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants