Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One approach you could take is to define an interface that contains all the methods that you would like to call from the mother application (called say <code>IMother</code>), and make the mother application implement this.</p> <p>Then you could update <code>IPlugin</code> to have a method like <code>void SetMother( IMother mother )</code> and when you load each plugin you could call this method on the plugin. That way each plugin would have the <code>IMother</code> reference from the beginning and could call methods as necessary.</p> <p>Regarding your question on plugininterface.dll, yes, both MainApplication and myPlugin are dependent on that dll (it is not just needed for development). If you want to avoid using an extra dll (having references to extra dlls isn't generally an issue) I would put the plugin interface in the same project as MainApplication. I'm not sure if I'm understanding your layout though, so if that doesn't answer your question please add more details as to how your projects/solution is configured.</p> <p>EDIT BASED ON COMMENT:</p> <p>I assume your layout is something like the following:<br> One solution file that contains three projects<br> One project for MainApplication<br> One project for myPlugin<br> One project for the plugin interface. </p> <p>You could move the code files for the plugin interface into the MainApplication project. That way MainApplication would not be dependent on anything else. Just take the .cs file from the plugin interface project and add it to MainApplication. You would then need to reference MainApplication from myPlugin, but that should be ok.</p>
    singulars
    1. This table or related slice is empty.
    1. POC# Plugin: access mother form and functions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScsm8118
    1. UScsm8118
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POC# Plugin: access mother form and functions
      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
    1. COplugin interface in the main app project would make more sense I think.
      singulars
      1. PO
      1. USSam Axe
    2. COThanks csm! I would just like to use as less dll's as possibly can, because the application itself is going to be single exe. When user downloads it, the app is gonna download all the plugins and save them in a dir. If main application is dependent on pluginInterface.dll, then it's not gonna work and I will need to use another application that is not dependent on anything to do all the work, which I don't want to do. Can you show me how can I define the pluginInterface in main application and the plugin using the code I provided please? thanks!
      singulars
      1. PO
      1. USuser1015551
    3. COThanks a lot, I'm gonna try it out now!
      singulars
      1. PO
      1. USuser1015551
 

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