Mark Kharitonov

My feedback

  1. 86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  NDepend User Voice » Code Model  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Mark Kharitonov supported this idea  · 
    An error occurred while saving the comment
    Mark Kharitonov commented  · 

    Our DI is entirely in code, we do not have any XML.
    Specifically, we use MEF for Dependency Injection. Everything is attribute based.

    I agree, that in order to be meaningful the DI analysis should have deep knowledge of the respective DI framework.

    NDepend is unlikely to have a single implementation for all. It will probably have a modular implementation with a module per DI framework and ideally an API to allow third parties to develop modules for other DI frameworks. Something like that.

    Non trivial, but essential if the call graph feature is to be supported in the future.

Feedback and Knowledge Base