5 results found
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.6 votes
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
Parse IoC Framewoks settings XML files to append on-demand defined dependencies to the NDepend code model.87 votes
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
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
- Don't see your idea?