dependencies - Plugin dependency best practices -


We have plug-ins that support an application through the interface; Plugins on the other hand have many of its logic and code There are plug-ins dependencies (project and DLL reference) beside the application interface for application libraries that display the application.

Application core libraries contain reusable components that can be used in plugins but if any of these components changes anyway, both plug-ins and applications are affected, because Both have dependencies.

Is it dependent on plugins dependent on system, which plug-ins are extended? What are the best practices on this issue?

Please share your thoughts and experiences.

Look at one, even if you are not developing in C #, this gives you some great ideas Will give

The simplest solution is to define a version system for plugins and cores, so the core can read which version of the plugin itself is needed to prevent load of a plugin like this Which was to be used with the previous version of the core.


Comments