Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>For current versons of Autofac: ( 2.0+, so anything you should be using today)</strong></p> <p>You register multiple <code>ILoggers</code> (for example):</p> <pre><code>var builder = new ContainerBuilder(); builder.Register&lt;ConsoleLogger&gt;() .As&lt;ILogger&gt;(); builder.Register&lt;EmailLogger&gt;() .As&lt;ILogger&gt;() .PreserveExistingDefaults(); //keeps console logger as the default </code></pre> <p>Then get all <code>ILogger</code>s:</p> <pre><code>var loggers = container.Resolve&lt;IEnumerable&lt;ILogger&gt;&gt;(); </code></pre> <p>You don't need to do anything special, just ask for an <code>IEnumerable&lt;T&gt;</code> of the desired type. Autofac has collection support out of the box, along with other <a href="http://autofac.readthedocs.io/en/latest/advanced/adapters-decorators.html" rel="nofollow noreferrer">adapters</a> that can wrap your components with additional functionality.</p> <p>This is the same usage as the pre-2.x ImplicitCollectionSupportModule, but baked right in.</p> <p><strong>For old versions (0.X - 1.4)</strong> </p> <p>Two ways:</p> <p>1) Use the collection registration</p> <pre><code>var builder = new ContainerBuilder(); builder.RegisterCollection&lt;ILogger&gt;() .As&lt;IEnumerable&lt;ILogger&gt;&gt;(); builder.Register&lt;ConsoleLogger&gt;() .As&lt;ILogger&gt;() .MemberOf&lt;IEnumerable&lt;ILogger&gt;&gt;(); builder.Register&lt;EmailLogger&gt;() .As&lt;ILogger&gt;() .MemberOf&lt;IEnumerable&lt;ILogger&gt;&gt;(); </code></pre> <p>Then:</p> <pre><code>var loggers = container.Resolve&lt;IEnumerable&lt;ILogger&gt;&gt;(); </code></pre> <p>which gives you an IEnumerable.</p> <p>or 2) You can use the ImplicitCollectionSupport module, which will make the code work like newer versions of Autofac:</p> <pre><code>builder.RegisterModule(new ImplicitCollectionSupportModule()); builder.Register(component1).As&lt;ILogger&gt;; builder.Register(component2).As&lt;ILogger&gt;; </code></pre> <p>Then resolve a collection of ILogger rather than looking for resolving all.</p> <pre><code>var loggers = container.Resolve&lt;IEnumerable&lt;ILogger&gt;&gt;(); </code></pre> <p>which gives you an IEnumerable, again.</p>
    singulars
    1. This table or related slice is empty.
    1. POAutofac: Resolve all instances of a Type
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPhilip Rieck
    1. USPhilip Rieck
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAutofac: Resolve all instances of a Type
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPerfect. Went for option one as its seems more efficient because the container "knows" what to put in the collection. Second option iterates though every registration in the container hierarchy looking for matching types.
      singulars
      1. PO
      1. UScrowleym
    2. CO@philip-rieck hi, what does it means container.resolve in autofac?. If you dont use autofac, in which way you can declare Ilogger interface? thank you...
      singulars
      1. PO
      1. USs_h
    3. CO@sebastian_h if you are not using autofac, this answer will have no meaning for you. You may want to look here instead: http://stackoverflow.com/questions/5646820/logger-wrapper-best-practice
      singulars
      1. PO
      1. USPhilip Rieck
 

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