Discussion for FogBugz Plugin developers
That's a fair objection, but no, right now you would have to write a single Plugin inheritor implementing all of the interfaces you want and then set up routing yourself -- at that point you could re-use the interface definitions in the classes to which you're routing.
What I do is to create a partial class like this:
MyPlugin.cs --> contains the class main definition with the constructor and the interface references
MyPlugin.PageDisplay.cs --> in this part I'd have the IPluginPageDisplay methods for instance
etc. (you can add as many parts as needed).
You can even have VS dispaly them in a nice nested way in the Solution Explorer, either by hand or by using an addin such as http://blog.laurent.etiemble.com/index.php?post/2006/12/08/101
While this does not really solve the issue of having one class only, it helps a lot to keep more complex plugins better organized and more maintenable (also in regards to source control).
This topic is archived. No further replies will be accepted.Other recent topics