Databases
StackOverflow2013
Postsdbo
PODependency Injection: Where should I inject? Who should control it?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODependency Injection: Where should I inject? Who should control it?
    primarykey
    data
    text
    <p>Disclaimer: Code written without a compiler, you should discard any syntax errors. :)</p> <p>I am wondering about what I am doing is "right".</p> <p>Currently, I have a Manager class with static methods. Those methods each call a method on my Repository class (eg. Manager.Get will call Repository.Get, and so on).</p> <p><em>The Repository implementation will be injected!</em></p> <p>Manager has a static field that references a singleton instance to itself, as well as a reference to an instance of the repository.</p> <pre><code>static Manager _me = new Manager(); [Dependency] public IRepository Repo; </code></pre> <p><strong>Note: This is how I currently do the resolving! I need feedback on this!</strong></p> <p>In the managers Ctor, I resolve the dependency</p> <pre><code>public Manager() { // Feedback would be nice on this as well! // I have a singleton reference to the container, // being set from the startup project. Repo = Singleton.UnityContainer.Resolve&lt;IRepository&gt;(); } </code></pre> <p>Manager's methods would look like this:</p> <pre><code>public static MyObject Get(int id) { return _me.Repo.Get(id); } </code></pre> <p>In my main program (e.g a Console application), I will register my implementation.</p> <pre><code>static void Main(string[] args) { var container = Singleton.UnityContainer = new UnityContainer(); // The implementation to inject, could change over time // to a MSSQL or MySQL, who knows? Hence the DI! var myXmlRepo = new XmlRepository("C:\My.xml"); // Register the instance container.RegisterInstance(myXmlRepo); container.RegisterInstance&lt;IRepository&gt;(myXmlRepo, new ContainerControlledLifetimeManager()); // Why do I need to register TWICE? } </code></pre> <p>So, to summarize my question:</p> <ol> <li>Is it a bad idea to use a singleton reference (not only to a container, but at all?) in the way shown above?</li> <li>Am I doing the resolving right? Or should I have used BuildUp somewhere? Should I have called Resolve from the startup projects code?</li> </ol> <p>Thank you for your time!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJeff
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODependency Injection: Where should I inject? Who should control it?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODependency Injection: Where should I inject? Who should control it?
      1. USPrateek Singh
      1. VTFavorite
    1. COYou don't need to register twice, the last line should do if you will resolve by interface. You can also make container create the instance of XmlRepo itself, just pass the parameter for the constructor: `container.RegisterType<IRepository, XmlRepository>("C:\My.xml", new ContainerControlledLifetimeManager())` but this will not return you the exact instance
      singulars
      1. PODependency Injection: Where should I inject? Who should control it?
      1. USRitro
    2. COYes, I do need to register twice - else it wont resolve it correctly. http://stackoverflow.com/questions/5770580/resolve-may-fail-depending-on-order-of-registerinstance-and-registertype/5774549#comment21181656_5774549
      singulars
      1. PODependency Injection: Where should I inject? Who should control it?
      1. USJeff
    3. COMine works without registering twice but endeed with `ExternallyControlledLifetimeManager` - not the `ContainerControlledLifetimeManager`
      singulars
      1. PODependency Injection: Where should I inject? Who should control it?
      1. USRitro
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload