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
StyleCop Analyzer not generating an xml anymore #126
Comments
Can you create a custom logger to solve this? Like they talk about here: And they say it is described here: I am not using that tool, but perhaps a custom logger can create a report in any of the supported formats of this tool. |
I was about to try that, but msbuild has a I'm going to try that tomorrow, but I'm not sure how the Parser is going to handle all the stuff before and after the relevant stuff. Also the file is not XML now... so I guess a new or different parser will then be required... |
The relevant output looks like this btw:
|
Should be no problem implementing a paraer for that. Can probably be done similar to CLangParser: |
Nice, in that case i just copy that parser, replace the regex with something like that: https://regex101.com/r/t2ZFbH/1 |
Add it as a new parser. I dont know if StyleCop2 or MSBuild might be fitting names. Is this the same format for all MSBuild output? Or the format is only for Stylecop? Add it here, and the docs will be automatically updated: You can see some reporters have some small explanation. You should add that fileLogger parameter in that text. Also add test case, like: |
Yeah I thought so too that MSBuildLogParser might be a better name as it hast the same format as regular msbuild warnings too. At least from what i've seen so far. Alright... i'll try my best =) |
is it an issue when the same warnings are twice in the output file? |
They are added to a Set. So duplicates will automatically be removed. |
The new Version of StyleCop is not generating an xml file anymore as mentioned here: DotNetAnalyzers/StyleCopAnalyzers#1178
Therefore the current StyleCop Parser does not find the report. Is there a way to get it to work again? Or is a new Parser required for this?
The text was updated successfully, but these errors were encountered: