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

SA1516 without a line number #3565

Closed
kglundgren opened this issue Oct 13, 2022 · 5 comments
Closed

SA1516 without a line number #3565

kglundgren opened this issue Oct 13, 2022 · 5 comments

Comments

@kglundgren
Copy link

I can't see the error anywhere in my files, and I can't double click on the error in the error list in Visual Studio to get to it either.
It comes from a "CSC" file apparently.

image

@bjornhellander
Copy link
Contributor

Hi! Based on the AD0001 about SA1201 throwing an exception, it looks like the StyleCop.Analyzers version you are using is too old for the c# language version you are using in your projects. There was a fix made in 2020 to protect from exceptions in SA1201, so that is why I assume that you are using an older version. I don't know if this is related to the thing you actually reported, but maybe we can focus on the AD0001 first, since that seems like a simpler problem? Can you upgrade to beta 435 and try again?

@kglundgren
Copy link
Author

Thanks for replying! I can't find the beta release in the Visual Studio nuget package management window. These are the versions I can see:
image
Is there another way to install the beta version?

@bjornhellander
Copy link
Contributor

There is a checkbox called "Include prerelease". See for example the screenshot from this question:
https://stackoverflow.com/questions/54984996/nuget-activate-include-prerelease-via-config-file

@kglundgren
Copy link
Author

After upgrading to version 1.2.0-beta.435 the warning went away. Thanks!

@sharwell
Copy link
Member

Duplicate of #3242

@sharwell sharwell marked this as a duplicate of #3242 Nov 28, 2023
@sharwell sharwell closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants