For a new project I am considering reusing an old C# plugin framework (I've used several times before) but am wondering if Castle Windsor would be better for my needs.
The plugin framework I was using implements late binding via the factory pattern to invoke custom plugin DLLs (with each plugin class library inheriting from a common interface IPlugin.) I always though that using the System.Activator class to create instances of custom libraries was a little slow, and that perhaps the overhead becomes a little heavy when there are let's say at least 50+ plugin instances instantiated concurrently. Ultimately I need to be able to land a solution that will allow custom design of new plugins that will not require the core framework (factory) to be recompiled. Can Castle Windsor facilitate my requirements and perhaps provide much better performance (less overhead) and improved handling (lifecycle management) vs. using my old factory pattern solution? -Matt -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
