Multiple forms with Multiple application using formstack

[Chintan]

HI,

I am using formstack for my multiple form application. But i dont have
only one application, i have 4-5 different dlls, which can push forms
using the formstack.

I am also using Visual inheritance, that is the common user interface
part that will be there in all the forms.

Suppose dlls are as below:
1)CommonUI.dll with form CommonUI.cs(Form with common
userinterface),Formstack.cs
2)A.dll with form A1.cs, A2.cs -- both inherited from CommonUI.cs
3)B.dll with form B1.cs, B2.cs -- both inherited from CommonUI.cs
4)C.dll with form C1.cs, C2.cs -- both inherited from CommonUI.cs

Now, the commonUI controls should be able to create objects of any of
the (A,B,C) dlls and pass the form to FormStack's Push method. If i
override the events then A will need to refer B,C also B will need to
refer A,C and C will also need to refer A,B. But logically it is not
fine. A should not be needing B,C and vice versa.

If i write default implementation in commonUI.dll only, then commonUI
will need to refer A,B,C as well as A,B and C will need to refer to
commonUI for inheriting visual inherited controls.So, it becomes
Circular reference.

The thing is that, with single application and all the forms in that
application, this all is working fine. But when i am trying to separate
them in different dlls this problems are coming. I havent seen anybody
using Visual Inheritance and Formstack together. But with single
application, this was working great. Now, when i am separating them in
different dlls, this has become the biggest problem we have ever.

Any ideas will be appreciated.
Thanks.

 

[Daniel Moth]

Rule of thumb:
1. Keep your application forms in one assembly: the exe
2. Use dlls for blind code (not even msgbox) and custom controls

If you want to ignore the rule of thumb...

Now, the commonUI controls should be able to create objects of any of
the (A,B,C) dlls and pass the form to FormStack's Push method. If i
override the events then A will need to refer B,C also B will need to
refer A,C and C will also need to refer A,B. But logically it is not
fine. A should not be needing B,C and vice versa.

Sorry, the above doesn't make sense to me. In particular I don't
automatically see why the dlls have to know about each other. Can you post a
small, basic, complete example demonstrating the problem?

Cheers
Daniel