Hope you find this reassuring; we're heading down the same route except that instead of forms we're using controls and docking them in the main form.
G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Jay Ayliff Sent: 18 April 2002 10:18 To: [EMAIL PROTECTED] Subject: Using System.Reflection to create Extensible Apps I have found this to work, and it seems to have enormous possibilities: - We can group logically related applications in the same DLL assembly - We can easily implement new versions of apps by either overwriting the DLL assembly or simply by changing the value of AssemblyFileName so the program looks in a different place for the new version. I am happy about other aspects of this development, e.g. passing data between the loaded form and the container. What I really want a warm feeling about is whether this use of System.Reflection is a viable way of creating an extensible application, or whether I am storing up trouble for myself further down the line. I await your gracious comments. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
