Another article of mine published on MSDN: Search Dynamically for Plug-Ins

12 Comments

• Congratulations again, Roy. You planning on keeping up at this pace?
  

• Hey Shannon. Yes. There's one more planned for publishing :)
  

• Hi Roy,
  
  
  
  great articles on the plug-in stuff and very interesting blog. Keep on the good work ;-)
  
  
  
  Alex
  

• Thanks very much Alex! :)
  

• Great article series Roy, much appreciated!
  

• Roy , keep going !!!
  
  and good-luck
  
  proud of you
  
  & love you ...
  

• Roy, keep the great work going !!
  

• congrats Roy! Keep'em coming...
  

• Looks like a good article and I'm interested in learning how to do this. I couldn't find the download link for the source. Am I missing something?
  
  
  
  Thanks!
  
  
  
  John
  

• I have implemented a similar solution to this article but I came across one problem. If a third party was to create a plugin for version 1.0.0.0 of our application, if we changed the application version to 1.0.1.0 the plugin would not work. Our current solution is to have configuration files that redirect the assembly binding but I was wondering if you was aware of any other methods without having to use configuration files?
  

• Russell:
  
  This is usually the problem with plugin mechanisms. That's why it's usually a good idea to leave the Plugin SDK interfaces in a separate assembly, which should almost never change, and have the plugins developers reference the never changing assembly. Saves lots of headaches.
  
  Of course, it also means that you need to do upfront design of all your plugin interfaces, which is always a good idea.
  

• BTW: the source code for all articles should be available now.