I've already created a UI framework based on the same strategy. It works
very well.
My MDI parent window is written in C# and I have "application modules"
that are dynamically discovered when the exe is started. The container
application, on startup, looks for assemblies that implement the
interf
Hello again Peter,
I checked it out again. The reason it didn't work was I was casting to
Form, but calling a Connect() method on our base class. Now I am casting to
our base class and it works fine. We now also have the added safeguard that
forms not based on the base class will fail.
Thanks ag
Hi Peter,
Thanks for that advice. What we are actually doing is creating our own base
class, inherited from Form, and having all the applications inherit from
the base class. This allows us to put various bits of communication,
database and security plumbing into the base class where it is hidden
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 h
Reflection works well for creating a modular program. I would recommend
using strong types more liberally. I assume VB allows you to call methods on
an Obj that do not exist and that it will use reflection to call those
methods. It would be better to cast your object into a Form. Here is the C#
sy
