Hi vwg team.
I am developing an application with this structure:
- a number of "Plugins", each being a .dll inheriting from Gizmox.WebGUI.Forms.UserControl
- a Main form loading dinamically from a custom directory the Plugins with a StreamReader and the Reflection.Assembly object.
This works pretty fine and allows me to have the \Plugins directory completely free with the assemblies never locked, allowing me to deploy anytime a new version of them without affecting the connected users.
I have only one problem:
in case the Plugins are directly referencing some OTHER assembly (i.e. standard Class Libraries) , i must put them in my main \bin directory to make the plugins work. Because the plugins loaded that way are working in the same memory space as main application.
And having those satellite assemblies in the same \bin with main application creates a lot of deploying problems (i.e. uploading a new version causes the reset of all connected client GUIs).
I could also post somewhere a sample application illustrating this.
Can you suggest a way to avoid this problem and be completely free with also those "second level" assemblies the same way i manage the plugins?
Hope i've explained well 
Luca.
- |
|