"// <auto-generated />" does not work anymore ?
See original GitHub issueHi there,
I have several files generated by SWIG and they contains the // <auto-generated />
comment at the second line.
The problem is that when I start an analysis, theses files are checked too !
It is intended to work, right ?
PS: I have also put it on the first line, no way !
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Auto-generated file errors after updating Gradle
I have an app that have a android library module that has an old gradle. After upgrading my gradle, I got this errors...
Read more >Why auto generated Factories do not extends or ...
There is no more to it. Making it extend each other to some abstract ... The factories are autogenerated only if the class...
Read more >VS2019 - v.16.1.1 - Code is not generated automatically on ...
My solution is to open the project using visual studio 2017 , upgrade the model from database and then go back in vs2019....
Read more >Enable or disable autogenerated binding redirects
On the Application page, uncheck the Auto-generate binding redirects option. If you don't see the option, you'll need to manually disable ...
Read more >Does the autogenerated excerpt not work with CPT UI?
In my custom posts the excerpts only work fine if typed in manually. There is no way to find a solution. It doesn't...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
CA1050 is a diagnostic from Visual Studios own code analysis. StyleCop’s rules all start with SA or in some rare cases SX. Does any StyleCop dignostics trigger for you?
@vd3d StyleCop Analyzers is not affected by the “Run Code Analysis on Build” option (i.e. it will always run whether or not that setting is enabled).