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

I am trying to build Error RS2003 Rule 'EF1001' was shipped in analyzer release '3.0.0', but is no longer a supported diagnostic for any analyzer. Add an entry for this rule in a 'Removed Rules' table to unshipped file. EFCore.Analyzers #28408

Closed
hounddog22030 opened this issue Jul 9, 2022 · 2 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@hounddog22030
Copy link

I have pulled the lastest 6.0 main into Visual Studio but get the compilation error:

Severity Code Description Project File Line
Error RS2003 Rule 'EF1001' was shipped in analyzer release '3.0.0', but is no longer a supported diagnostic for any analyzer. Add an entry for this rule in a 'Removed Rules' table to unshipped file. EFCore.Analyzers C:\Users\17034\source\repos\hounddog22030\efcore\src\EFCore.Analyzers\CSC 1

How do I "resolve" this, get around this?

@roji
Copy link
Member

roji commented Jul 9, 2022

Which exact branch did you check out, and which commit are you trying to build (please provide the SHA1)? This happens because of dotnet/roslyn-analyzers#5828, but we already hacked around it (in 6.0 it was never present).

My guess is that you're on some old 7.0 commit.

@hounddog22030
Copy link
Author

Your question made me investigate. I merged 6.0 down in and the issue went away. Thanks.

@roji roji added the closed-no-further-action The issue is closed and no further action is planned. label Jul 10, 2022
@roji roji closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

2 participants