Interface addons

[flossy]

When adding interfaces, whats the recomended way of doing it?
Right now i added a class to the mig-project that calls a supportlibrary, and that works ofc. But by the looks of it i could just aswell have that class in an external dll and configure it to load the interface from there, if that works?

So the question comes down to if the plan is to keep a clean hg-core with a bunch of addons that you can add/remove at your will, or if the interface support is planned to be included in hg/mig?

There are benefits to both i guess, but keeping them as plugins will let users choose what to run and not but complicates the configuration a bit. that would allow for nuget support for addons aswell.

Anyway, the main question is. if i make an interface, is it then prefered to be kept as a separate dll or included in the main mig library?

/C

[bkenobi]

Gene will give a better answer, but X10 is added with XTenLib.dll.  If a change is made to X10, recompiling that dll and replacing it updates how HG interacts with X10.

[flossy]

Ya, but X10 also has its MIGInterface placed in the mig library aswell, that handles the calls to the external dll (the same setup as im using for tellstick).
But depending on how mig loads the interfaces, it isn't even needed to be placed there. It could be completely contained in the external dll.