Library tutorials & articles
Writing Plugin-Based Applications
Introduction
Doing this in .NET is actually slightly easier than in COM, in my opinion, and far more powerful. For instance, getting your COM plugins to show an interface within a dialog shown by the host application was a bit of a nightmare, and required calls to SetParent and inventive use of window styles to get working properly. This is trivial in .NET because of the Windows Forms architecture. The process of opening and inspecting DLLs in .NET is much the same.
Plugin Architecture
The best way to implement plugins in your application is with Interfaces. It is beyond the scope of this tutorial to explain interfaces, but they are in essence a contract. Any class implementing an interface must implement every member on the interface, so any application that knows about the interface knows exactly what to expect.
You start off by building a class library with the interface(s) in. Usually you would use at least two. The minimum you could have is one, which every plugin class would implement. However, in practice you generally need another interface, which the host implements so the plugins have some way of communicating back to the host application. When the interface class library has been built, you write the host application which references this library, and can inspect any number of DLLs to see if they contain classes that implement these interfaces. At this point you can develop the plugins themselves, again referencing the class library to implement those interfaces.
Related articles
Related discussion
-
How to write a query set to excel using vb.net
by BarbaMariolino (1 replies)
-
Very Urgent regarding deleting the images from a folder
by rameshbandi (2 replies)
-
Block Accessing MSSQL 2000
by militia (0 replies)
-
.NET Developer in Ghana Required....
by sysview (0 replies)
-
Sending SMS to mobile using secure gateway from VB.net 2008 c#
by pratikasthana17 (0 replies)
Related podcasts
-
xpert to Expert: Inside Concurrent Basic (CB)
"Concurrent Basic extends Visual Basic with stylish asynchronous concurrency constructs derived from the join calculus. Our design advances earlier MSRC work on Polyphonic C#, Comega and the Joins Library. Unlike its C# based predecessors, CB adopts a simple event-like syntax familiar to VB progr...
hi
when i run the host i found this error : Warning 1 Could not resolve this reference. Could not locate the assembly "Interfaces". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Plugin 1
"PluginSample.Interfaces.IPlugin" is not defined
can u help me to splve this problem
thanks
!--removed tag-->Just add event handlers to the menu items before returning from InitializeMenu, e.g.
[quote]menu1.Click += new EventHandler (nameOfCallbackFunction);[/quote]
I found a very easy way to add controls to the host.
Dim Menu As New ToolStrip
Dim menu1 As New ToolStripMenuItem("Plugin")
menu1.DropDown = CreateCheckImageContextMenuStrip("Calculate")
Menu.Items.Add(menu1)
Menu.Dock = DockStyle.Top
Return Menu
End Function
Me.ToolStripContainer1.TopToolStripPanel.Controls.Add(objPlugin.InitializeMenu)
The only thing i did not figure out yet is how to handle when you click on the control.
I rewrote your application in C# and everthing works except one thing.
After loading assembly and creating plugin instance I am casting plugin instance to plugin interface and I get excepion "Specified cast is not valid"
I have no idea what is wrong.
I needed the plug in functionality to swap and update plug-ins on a regular basis, for an ASP.Net application. However, it seems I must shut down the site completely to replace an existing plug-in with a new version...
Great article!
This will come in very handy with an application I have in mind
Just a note about using this in VB2005 (I'm using Express edition right now, hopefully I'll upgrade):
The CreateInstance method of the PluginServices works fine, and does return an instance of the class that can be used but only when put into an Object type.
You don't have the full list of functions and subroutines available to you using the object.
When using the DirectCast, to cast the instance to an variable declared as the Interface - it doesn't like that cast and throws an exception.
To fix this do what Prozac mentiond - change the references of [Assembly].LoadFrom() to [Assembly].LoadFile() and it works fine.
Thanks for the great article!
I think your article is great, i'm looking for it for months, and finally...
I just have a question:
If I want that a plugin add a button ont the host form, is it possible? can you help me please?
thanks in advance,
Ivan
The complete code is available in the source code, however I'll post it for you anyway.
Public Structure AvailablePlugin
Public AssemblyPath As String
Public ClassName As String
End Structure
Enjoy!
I noticed that when I used [Assembly].LoadFrom(), it kept on loading the first plugin that was initially loaded,
to fix this; use [Assembly].LoadFile() insted.
DotNet Framework 1.1, Visual Studio 2003, Visual Basic.NET.
I can't get AvailablePlugin to work. VB.NET reports that
"Type 'AvailablePlugin' is not defined." Has anyone else had this problem?
Hi.
I've been trying to find the way of doing an application with pluggable components over vb6, but have not found any help. I read the subject of this article and was very excited but when I realized it was about .net I got frustrated. Could you please explain me how it is possible to make a plugin-based app in vb6.
Thanx
malloc
This thread is for discussions of Writing Plugin-Based Applications.