Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I understand your question correctly, you want to force a class to implement a number of different interfaces, the list of interfaces will grow with time but will have some properties in common.</p> <p>The common property part you have solved with your <code>IService</code> interface. Something like this, I presume</p> <pre><code>interface IService { DateTime LastRuntime { get; set; } } interface IGetAlarms : IService { string GetAlarms(); } interface IGetDiagnostics : IService { string GetDiagnostics(); } </code></pre> <p>The growing list of interfaces that a class will have to implement you can also solve in a similar fashion. Create a "composite" interface which inherits from all the interfaces you wish your class to implement</p> <pre><code>interface IComposite : IGetAlarms, IGetDiagnostics {} class MyClass : IComposite { ... } </code></pre> <p>When you let the <code>IComposite</code> interface inherit a new interface, the class will have implement the new interface too.</p> <p>EDIT</p> <p>In response to your clarification; in that case you should not share the specification of the <code>LastRuntim</code>e property, but declare it in each individual interface. In the implementing class you can use <code>Explicit interface member implementation</code></p> <pre><code>class MyClass : IComposite { DateTime IGetAlarms.LastRuntime { get; set; } DateTime IGetDiagnostics.LastRuntime { get; set; } ... } </code></pre> <p>However, AFAIK it is not possible to force the implementing class to explicitly implement each individual interface</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to force multiple Interfaces to include the same properties?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter
    1. USPeter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI should have mentioned in my initial post that the properties I would like to enforce in all the Interfaces must be specific to each Interface. So, using my initial example, the class that implements IGetAlarms and IGetDiagnostics will be able to store different values for the IGetAlarms.LastRuntime and IGetDiagnostics.LastRuntime properties. The problem I'm trying to solve here is making sure all Interfaces support their own implementation of LastRuntime. I'm unable to use abstract classes in this case, because my derived class needs to be able to implement multiple services.
      singulars
      1. PO
      1. USJed
    2. COThanks for your input, Peter.
      singulars
      1. PO
      1. USJed
 

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