6 results found

1. Add support for enumerating count of suppressions/attributes

   We have a situation where SuppressMessage attributes are being used very liberally in order to remove issues NDepend finds from the tech debt metrics. This is an unintended side effect of engineers attempting to get their tech debt percent to zero. I don't believe that this aligns with the spirit of the tool and I would like to create some custom rules/gates around issue suppressions in order to discourage their overuse. I am of the strong opinion that these attributes should be used sparingly and an excessive number of these attributes is a sign of tech debt, as it means we are intentionally ignoring tech debt.

   I can use code such as the following to create a custom gate that fails at a certain number of suppressed issues:
   /// <QualityGate Name="Excessive Issue Suppressions" Unit="issues" />
   failif count > 10 issues
   warnif count > 5 issues

   from i in context.IssuesSet.AllSuppressedIssues
   select new { i, i.Severity, i.Debt, i.AnnualInterest }

   However, I would like to actually implement a rule that I can use to raise an issue based on the number of attributes used. I can formulate a rule to determine distinct number of types that specifically use the attribute:

   from t in AttributeTargets

   where t.AttributeClassesThatTagMe.WithName("SuppressMessageAttribute").Any()

   select new {
   t,
   Count = t.AttributeClassesThatTagMe.WithName("SuppressMessageAttribute").Count()
   }

   However, there does not appear to be a way to give me a count of all the attributes that are decorating an AttributeTarget. The above query always returns a Count of 1. So for example, applying 4 attributes to one class will still only count as one occurrence in the CQLinq script. Such a rule becomes completely impossible if a GlobalSuppressions class is used, or any case when the attributes are all targeted to the assembly, so even if 20 SuppressMessage attributes are used, only one (just for the assembly) will count in the CQLinq result.

   Please provide a method to get the count of attributes of a specific type.

   Additionally, it would be good to know if there are suppressions that are not actually suppressing any issues, since often a suppression is added for a false positive, which is later fixed by NDepend. This would require adding actual suppression definitions to the code model. This would help to clean up suppressions that are added but are no longer needed and should be removed.

   We have a situation where SuppressMessage attributes are being used very liberally in order to remove issues NDepend finds from the tech debt metrics. This is an unintended side effect of engineers attempting to get their tech debt percent to zero. I don't believe that this aligns with the spirit of the tool and I would like to create some custom rules/gates around issue suppressions in order to discourage their overuse. I am of the strong opinion that these attributes should be used sparingly and an excessive number of these attributes is a sign of tech debt, as it means… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Create custom extension methods

   NDepend is great but it definitely won't be able to cover all requirements for all customers, so, it'll be much better if we can extend NDepend !
   In my organization, we've a lot of rules that share some logic so I need to encapsulate this logic in a single extension method either in a C# dll or a CQLinq query and reuse it anywhere.

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Be able to query methods parameters types

   NDepend code model should propose a getter IType[] IMethods.ParametersTypes to be able to write certain code queries and rules, like security related ones.

   42 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Integrate with IoC Framewoks

   Parse IoC Framewoks settings XML files to append on-demand defined dependencies to the NDepend code model.

   90 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   16 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Parse VB.NET code

   Parse VB.NET code the same way C# code is parsed, to gather the code metrics # Lines of Comment and Source Code Cyclomatic Complexity from VB.NET code bases.

   70 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Basic support for managed C++

   I stumbled upon that properties in the API do not work correctly with managed C++ projects. For example IAssembly.VisualStudioProjectFilePath always returns null in case of a vcxproj or ISourceFile.Language always returns SourceFileLanguage.Other.
   This is not about full support for managed C++ but basic things like the ones above would be great if they work when working in a heterogenous environment.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Code Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close