Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>An interface says how something should work. Think of it as a contract or a template. It is key to things such as Inverson of Control or Dependancy Injection.</p> <p>I use Structure Map as my IoC container. This allows me to define an interface for all of my classes. Where you might say </p> <pre><code>Widget w = new Widget(); </code></pre> <p>I would say </p> <pre><code>IWidget w = ObjectFactory.GetInstance&lt;IWidget&gt;(); </code></pre> <p>This is very powerful in that my code isn't saying necessarily what a Widget truely is. It just knows what a Widget can do based on the interface of IWidget.</p> <p>This has some great power to it in that now that I am using an IoC container I can do a couple more nifty things. In my unit tests where I need to use a Widget I can create a mock for Widget. So say that my Widget does something very powerful by way of connecting to a database or a web service, my mock can simulate connecting to these resources and return to me stubbed data. This makes my test run faster and behave in a way that is more reliable. Because I am using StructureMap I can tell StructureMap to load the real implementation of my Widget during production use of my code and the mocked version of the Widget during testing either programatically or by configuration.</p> <p>Also, because I am using an IoC container I can provide cool new features to my application such as writing three different ways to cache data. I can have a local developer box cache using a tool such as Lucene.NET for a local cache. I can have a development server use the .NET cache which runs great on one box. And then I can have a third option for my production servers use a cache layer such as MemCache Win32 or Velocity. As long as all three caching implementations conform to the same interface, their actual implementation doesn't concern me (or my code) at all. I simply ask StructureMap to go get the current environments implementation and then go to work.</p> <p>If you follow Dependency Injection at all then interfaces come in handy here also with an IoC container such as StructureMap in that I can declare the usage of a class by way of an Interface in the constructor of my class.</p> <pre><code>public class Widget(IWidgetRepository repository, IWidgetService service) : IWidget { //do something here using my repository and service } </code></pre> <p>And then when I new up an instance of Widget by way of StructureMap such as this</p> <pre><code>IWidget widget = ObjectFactory.GetInstance&lt;IWidget&gt;(); </code></pre> <p>Notice that I am not specifying the repository or service in the constructor. StructureMap knows by way of the interfaces specified in the constructor how to go get the appropriate instances and pass them in too. This makes very powerful and clean code!</p> <p>All from the simple definition of Interfaces and some clever usage of them!</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat are some advantages to using an interface in C#?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrew Siemer
    1. USAndrew Siemer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat are some advantages to using an interface in C#?
      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. VTUpMod
    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. This table or related slice is empty.
 

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