My feedback

1 result found

1. Integrate with IoC Framewoks

   87 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  ·  NDepend User Voice » 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
   Mark Kharitonov supported this idea  ·  April 30, 2020
   An error occurred while saving the comment
   Mark Kharitonov commented  ·  August 11, 2016  ·  Edit…  ·  Delete…

   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.

   Save Submitting...