How do I add a property to rules in a custom code analyzer?

Question

0.00/5 (No votes)

See more:

I'm putting together a custom code analyzer to run against Visual Studio 2015 solutions and I would like to add a property to control it by date.

When in place then the rule (or rule set) would only be applied to code modified on or after the set date.

Is this possible and where are the best sources of information?

What I have tried:

Extensive online research that has yielded nothing.

I also added a new variable to the section of the analyzer where the DiagnosticID is set but I was not able to access it anywhere else.

New Idea Forming! What if I try passing it is as an argument?

Update
I tried that idea using a constructor - no joy. Now I will try reading from a config

And for next week...
CodeCracker checks for something like <auto-generated> in a header comment to skip scan on autogenerated files.
seen here

and on stackoverflow

I'm thinking of adding a comment <qa-checked> when the analyser runs. Then add a precompile event to the compiler to remove this from modified code.

The analyzer will be instructed to skip any code marked <qa-checked>

Posted 6-Sep-18 23:49pm

Ger Hayden

Updated 7-Sep-18 18:55pm

v5

Add a Solution

Comments

Richard MacCutchan 7-Sep-18 8:55am

What is the problem? Comparing dates should not be difficult.

Ger Hayden 7-Sep-18 9:33am

True, the date comparison is the easy part. The difficulties lie in supplying a seed date to the analyzer, and getting the last modified date of the source file, say as opposed to the date it was checked out of source control.

Another option I am considering is to only apply the rule if the code has changed since the last run of the rules - if I can come up with an efficient convention for marking a code file as 'Analyzed'.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Gerry Schmitz · Answer 1 · 2018-09-07T18:56:00

Solution 1

Add "meta data" to the (vs) project for your "seed data", last modified date, etc.

Create a "macro" to add your meta data as a "project item"; then use a "reflection" of sorts to kick off the analyzer; results are added back in to the (vs) project / solution.

Posted 7-Sep-18 18:56pm

Gerry Schmitz