Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could define interfaces for your types/services that your evaluation-provided code supports, but doesn't provide. Then you could use <a href="http://mef.codeplex.com/" rel="nofollow">a plugin framework like MEF</a>, which is built into the .Net Framework (v4.0).</p> <p>MEF will do the reflection and assembly enumeration for you. You just have to define simple extension points in your code.</p> <p>Here is some basic documentation for MEF. It might be specific to the Codeplex version of the code (not sure) but it shouldn't be too old, and should give you a good idea of how it works:</p> <p><a href="http://mef.codeplex.com/wikipage?title=Guide&amp;referringTitle=Documentation" rel="nofollow">http://mef.codeplex.com/wikipage?title=Guide&amp;referringTitle=Documentation</a></p> <p><strong>Alternative ideas</strong></p> <p>You might want to solve this with licensing rather than distribution.</p> <p>You're going to have to solve the licensing problem anyhow, so you can collect money from users, and so you can sue people who grievously violate your copyright.</p> <p>If your code is worth distributing, you won't be able to prevent distribution. Piracy is not preventable.</p> <p>And most licensed code I've used recently have full-featured but timed trials, and phone home. They install all the code, but simply disable parts of it if they aren't licensed. It is hard for someone to know if they want to pay for your advanced features if they can't try them out :)</p>
    singulars
    1. This table or related slice is empty.
    1. PODetecting if a class/type is defined prior to compiling
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMerlyn Morgan-Graham
    1. USMerlyn Morgan-Graham
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm not sure how MEF would work here. We don't have control over the application, only a piece of code someone can use in their own code, all of which is used in the application (this is a game engine if it matters)... Distribution in this case has no real installation. To simplify, you would just get some files to add to a project just as if you had written the code. If the file is there, the type is there. We do declare licensing but it is rather simple in nature. You can use it if you don't redistribute, etc. We don't even worry about the dishonorable few in the community.
      singulars
      1. PO
      1. USRafe
    2. CO@Rafe: You said "files" in your OP, which I took to mean assemblies. Nearly all non-open-source .Net projects are distributed as assemblies, so you definitely have a special case here. That's fine and well, but that's why I didn't say more than just "use MEF" :) If you are distributing the *plugins* as assemblies (the accepted answer will only work if you are), then you could use MEF. You'd distribute an assembly that contains just the plugin interfaces, use those interfaces to make extension points in your source files, and implement those interfaces with your plugins.
      singulars
      1. PO
      1. USMerlyn Morgan-Graham
    3. CO@Rafe: It is up to you if MEF provides enough benefit to warrant using it. You're going to have to define a contract between the plugin and the code anyhow, and it will be easier to write code against an interface than it will against `object`. This will also give good perf (just virtual function calls once the type has been loaded). Other solutions involve you either calling with extended use of reflections (every call, property access, etc), using `dynamic` to do the same, or possibly compiling dynamic methods (see: https://github.com/ninject/ninject/wiki/How-Injection-Works)
      singulars
      1. PO
      1. USMerlyn Morgan-Graham
 

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