Jump to content
Xtreme .Net Talk

Recommended Posts

Posted
I'm developing an application that consists of a core user interface module and multiple content modules that plug into that core user interface and fill up the application workspace. I'd like to design the program so I can later add a .dll in the folder, update a .dat file (or something) and have the program automatically detect and load the new module on launch. Is this a pipe dream? My fallback plan is to have the core user interface .dll be called by a launcher module. That way, I can manually load the different modules from the launcher and update only the launcher module when I'm adding new modules. Anyone got any ideas?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...