Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need a contract(interface) and a metadata contract (interface):</p> <pre><code>public interface ICarPart{ int SomeMethodFromInterface(); } public interface ICarPartMetadata{ string /*attention to this!!!*/ NameCarPart { get; } /* Only for read. */ } </code></pre> <p>Then you export your parts:</p> <pre><code>[Export(typeof (ICarPart))] [ExportMetadata("NameCarPart","SteeringWheel")] /* is string!! */ public class SteeringWheel : ICarPart { public int SomeMethodFromInterface(){ ... //your stuff } } [Export(typeof (ICarPart))] [ExportMetadata("NameCarPart","Engine")] /* is string!! */ public class Engine : ICarPart { public int SomeMethodFromInterface(){ //Each method have diferent behavior in each part. ... //your stuff } } [Export(typeof (ICarPart))] [ExportMetadata("NameCarPart","Brakes")] /* is string!! */ public class Brakes : ICarPart { public int SomeMethodFromInterface(){ //Each method have diferent behavior in each part. ... //your stuff } } </code></pre> <p>Then you can import with ImportMany and Lazy:</p> <pre><code> [ImportMany()] IEnumerable&lt;Lazy&lt;ICarPart, ICarPartMetadata&gt;&gt; carParts = null; public void Importing(){ ... ... foreach (Lazy&lt;ICarPart,ICarPartMetadata&gt; item in carParts){ switch (item.Metadata.ICarPartMetadata.ToString()){ case "SteeringWheel": item.Value.SomeMethodFromInterface(); break; case "Engine": item.Value.SomeMethodFromInterface(); break; case "Brakes": item.Value.SomeMethodFromInterface(); break; default: ... break; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POC# MEF: Exporting multiple objects of one type, and Importing specific ones
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGalled
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POC# MEF: Exporting multiple objects of one type, and Importing specific ones
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is the advantage of this method over the one Adam proposes? Wouldn't this method require more overhead, and wouldn't this still at one point import ALL objects, only accessing methods of the ones you wish to use (i.e. those defined as cases)? If I end up with over 100 objects, this would hinder performance on plugins which only access 1 or 2 of those wouldn't it?
      singulars
      1. PO
      1. USBen K.
    2. COIn case you need a few imports you can use the Adam method. In other hand, the Lazy class is useful when you have a lot of imports. -> "Lazy is actually used when your plugins are heavy and need large amount of memory" http://dailydotnettips.com/2011/09/02/getting-lazy-with-mef/
      singulars
      1. PO
      1. USGalled
    3. COAdditionally, you need a contract to ensure that your solution will be maintained over time since with a contract you can alter your export class without touch the main project. If you put the names without contracts will be very dependent on the parts and you will lose some MEF benefits.
      singulars
      1. PO
      1. USGalled
 

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