Module hookup on a fly:

  • Thread starter Thread starter Ivan Demkovitch
  • Start date Start date
I

Ivan Demkovitch

Hi!

I will try to explain what I want to do:

Here is a history:

In VB6 I was doing this:

1. DB have projectname.classname stored for each "module"
2. Classes had same interface. All "modules" was ActiveX exe files.
3. Main launcher program was responsible for logging into DB, populating
menus, extracting modules info. Then it would create needed object using
Late binding.

This way, just by ensuring that ActiveX exe have public class with defined
interface I was able to create "add-ons" without modifying/recompiling whole
application.

How would I do it in .NET?

Any related reading, pointers?

TIA
 
Ivan Demkovitch said:
Hi!

I will try to explain what I want to do:

Here is a history:

In VB6 I was doing this:

1. DB have projectname.classname stored for each "module"
2. Classes had same interface. All "modules" was ActiveX exe files.
3. Main launcher program was responsible for logging into DB, populating
menus, extracting modules info. Then it would create needed object using
Late binding.

This way, just by ensuring that ActiveX exe have public class with defined
interface I was able to create "add-ons" without modifying/recompiling whole
application.

How would I do it in .NET?

Any related reading, pointers?

TIA
Click to expand...

Creating a Plug-In Framework:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/pluginframework.asp

Erik
 
Back
Top