92 results found

1. Be able to run R# "refactor"-commands based a NDepend query result

   Query code base in order to modify.

   ReSharper is best in facilitating refactoring.
   NDepend is best in facilitating code analysis and locating pieces of code.

   Solution: integrate the ReSharper and NDepend in any suitable way.

   1 vote

   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  ·  Visual Studio Integration  ·  Edit…  ·  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

   Submit Rating

2. LCOM Metric Should Not Include Property Accessors

   Property accessors usually only use 1 field. If they are used to compute the LOCOM metric then the result can be very misleading.

   1 vote

   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  ·  Edit…  ·  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

   Submit Rating

3. New to NDepend

   Please make the setup a bit easier to understand. I am a new user for Ndepend and i spent 30 mins trying to create a dependency graph of a existing project and in the end just gave up!

   1 vote

   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…)
   1 comment  ·  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

   Submit Rating

4. A 'Hound' like product for .Net projects

   I recently ran across a new project called 'Hound' http://robots.thoughtbot.com/introducing-hound that help developers fight the smaller code quality issues by commenting on github pull requests. This made me think of NDepend as a Service and would be a nice way to integrate NDepend into my workflow - by simply commenting on offending lines of a pull request a team could start to have an automated way of having the team fix things that might otherwise be missed. I really like how hound talks about removing the 'human' from some of the littler issues.

   I could see this starting out as a Freemium thing, where NDepend provides some really basic help, and then for paid plans you could put a project file in your repo and start getting even more advanced assistance.

   I realize that the kind of analysis that NDepend does is at a macro code level, hound is very much a line by line micro level. So I am not sure how directly applicable NDepend will be, but some kind of web hook analysis of a github repo would indeed be nice.

   Once there is a SaaS style offering the historical analysis of a project would be very interesting as well.

   I recently ran across a new project called 'Hound' http://robots.thoughtbot.com/introducing-hound that help developers fight the smaller code quality issues by commenting on github pull requests. This made me think of NDepend as a Service and would be a nice way to integrate NDepend into my workflow - by simply commenting on offending lines of a pull request a team could start to have an automated way of having the team fix things that might otherwise be missed. I really like how hound talks about removing the 'human' from some of the littler issues.

   I could see this starting out as… more

   1 vote

   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  ·  Build Process Integration  ·  Edit…  ·  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

   Submit Rating

5. IVisualStudioManager.GetAssembliesFromVisualStudioSolutionOrProject(IAbsoluteFilePath visualStudioSolutionOrProjectFilePath) not working.

   Our Requirement:
   1) Developer should be able to find the dependencies of any selected assembly or file (class level) in the solution.
   2) Integrate to build system. The tool should check for allowed/disallowed dependencies. The build should fail if there are disallowed dependencies.

   Our Approach:
   To satisfy the above mentioned, we tried to extend the NDepend.PowerTools by creating a new tool in the same solution.
   In the tool class, we tried to use nDepend dlls to get the dependencies of all assemblies/classes in the solution. The input for the tool is the solution file.

   Problem we faced:
   After selecting our tool from menu and after selecting the solution file, we are not able to get all the assemblies in the solution.
   The below mentioned method is not returning the actual assemblies which exists in the solution, instead its returning some random assemblies which are outside the solution.
   IVisualStudioManager.GetAssembliesFromVisualStudioSolutionOrProject(IAbsoluteFilePath visualStudioSolutionOrProjectFilePath)

   Our Requirement:
   1) Developer should be able to find the dependencies of any selected assembly or file (class level) in the solution.
   2) Integrate to build system. The tool should check for allowed/disallowed dependencies. The build should fail if there are disallowed dependencies.

   Our Approach:
   To satisfy the above mentioned, we tried to extend the NDepend.PowerTools by creating a new tool in the same solution.
   In the tool class, we tried to use nDepend dlls to get the dependencies of all assemblies/classes in the solution. The input for the tool is the solution file.

   Problem we faced:
   After selecting our… more

   1 vote

   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  ·  NDepend.API  ·  Edit…  ·  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

   Submit Rating

6. Maker possible to analyze some assemblies by right-clicking them in the Windows Explorer
   1 vote

   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  ·  UI - Ergonomy  ·  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

   Submit Rating

7. Update the GUI look and feel to a WPF + responsive GUI

   • The usage/look/feel is kind of clunky, with so miscellaneous delays and microadjustments, which make it feel slow.
   • Several panels are having a 'not really adapted' display.
   • A responsive display and adjustments would be much welcome.
   • Adding a smart column adjustment (put the mouse cursor between two column titles, the cursor becomes a left-right double arrow, then double click will make the collumn adjust to minimum width without cutting the largest row) would be much welcome.
   • etc
   1 vote

   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  ·  UI - Ergonomy  ·  Edit…  ·  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

   Submit Rating

8. IDesign

   Any plans in the works to create rules that enforce IDesign practices & principles (http://www.idesign.net/)?

   1 vote

   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…)
   6 comments  ·  Code Rule and Query  ·  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

   Submit Rating

9. Improve management of rules shared between projects

   In addition to sharing custom rules between projects I want to be able to enable/disable rules among all my projects. I currently have 5 active ND projects, so if I want to turn off, for instance, "Nested types should not be visible" for all my projects, I have to go uncheck it in each project. Every time I tweak my rules, I have to go repeat these tweaks in all my ND projects.
   Some sort of meta-project rules management would be an enormous effort saver.
   In addition, once a set of "standard rules" are decided upon, it would be nice to be able to create new projects and have those rules be the default.

   In addition to sharing custom rules between projects I want to be able to enable/disable rules among all my projects. I currently have 5 active ND projects, so if I want to turn off, for instance, "Nested types should not be visible" for all my projects, I have to go uncheck it in each project. Every time I tweak my rules, I have to go repeat these tweaks in all my ND projects.
   Some sort of meta-project rules management would be an enormous effort saver.
   In addition, once a set of "standard rules" are decided upon, it would be nice… more

   1 vote

   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 Rule and Query  ·  Edit…  ·  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

   Submit Rating

10. Add a minimal deployment option for build agents

    Although admittedly NDepend isn't a huge product, it would be helpful if there was a secondary deployment option which was just NDepend.Console.exe and its dependencies. No GUI tools, power tools, integration extensions etc. Just the absolute basics so that you can easy stick it on a build agent or in SCC as part of a tools folder without including stuff that a build agent would never use.

    Of course, this now has its own problems as v7 seems to use an activation model whereas with v6 you could just include the license file to your agents. (Not to mention the console application for some reason has indirect references to the DevExpress WPF GUI components)

    Although admittedly NDepend isn't a huge product, it would be helpful if there was a secondary deployment option which was just NDepend.Console.exe and its dependencies. No GUI tools, power tools, integration extensions etc. Just the absolute basics so that you can easy stick it on a build agent or in SCC as part of a tools folder without including stuff that a build agent would never use.

    Of course, this now has its own problems as v7 seems to use an activation model whereas with v6 you could just include the license file to your agents. (Not to mention the… more

    1 vote

    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…)
    1 comment  ·  Build Process Integration  ·  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

    Submit Rating

11. Summary report for all projects analyzed

    To have a widget or page that summarizes on one view ALL builds/projects with a analysis report for a simplistic view of all metrics available.

    1 vote

    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  ·  Dashboard  ·  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

    Submit Rating

12. Show rules violated by code elements in VS code editor and update status live

    A visual indicator indicates in the VS code editor for each code element (method, field, type, namespace) if it violates one or several rules.

    From this visual indicator it is possible to jump to the code rule(s) violated)

    The rule status would be updated asynchronously after 2 to 5 seconds (depending on the size of the code base) each time the user types and reach a compilable status.

    0 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  ·  Visual Studio Integration  ·  Edit…  ·  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

    Submit Rating