indikad wrote:Having to close and open Jiwa each time when make a change in plugin code ( to see the effects of the changes ) can be a bit cumbersome. Is there a way around ?
Hi Indika,
Unfortunately not at this time.
The problem is that once an assembly is loaded into an application domain, it cannot be unloaded. So, any subsequent changes to the code for a plugin will mean that the application domain (ie: Jiwa) needs to be unloaded before the plugin assembly can be recompiled and reloaded.
I understand it can be frustrating developing plugins this way - so I'll post a tutorial in the coming days showing how to use a surrogate Jiwa application within Visual Studio to let you develop a plugin within Visual Studio (allowing edit and continue, etc) - and then how you transfer the Visual Studio code to a Jiwa plugin.
Mike