T
Tom
Let's assume I have the following libraries:
MainLib (DLL)
MyControl (.NET user control)
Now MyControl needs to call MainLib, so I have a reference to MainLib
in MyControl. Let's then assume that I want to put a new form
(MyNewForm) in MainLib, but this form requires MyControl (i.e. I will
drop a copy if MyControl onto the MyNewForm). This would require me to
put a reference to MyControl in MainLib. Now I have MainLib referencing
MyControl, and MyControl referencing Mainlib!
Would this kind of circular reference even work? My problem is in what
order would something like this be compiled? I would think I would
first have to compile MyControl, then MainLib; but as soon as I
recompile MainLib the reference to MainLib in MyControl is now not
'current'...
Ugh, it hurts my head just thinking about this... I suppose the better
way would just be to make MyNewForm into it's own DLL, but was
wondering if something like the above scenario would work or is it even
recommended?
Thanks.
Tom
MainLib (DLL)
MyControl (.NET user control)
Now MyControl needs to call MainLib, so I have a reference to MainLib
in MyControl. Let's then assume that I want to put a new form
(MyNewForm) in MainLib, but this form requires MyControl (i.e. I will
drop a copy if MyControl onto the MyNewForm). This would require me to
put a reference to MyControl in MainLib. Now I have MainLib referencing
MyControl, and MyControl referencing Mainlib!
Would this kind of circular reference even work? My problem is in what
order would something like this be compiled? I would think I would
first have to compile MyControl, then MainLib; but as soon as I
recompile MainLib the reference to MainLib in MyControl is now not
'current'...
Ugh, it hurts my head just thinking about this... I suppose the better
way would just be to make MyNewForm into it's own DLL, but was
wondering if something like the above scenario would work or is it even
recommended?
Thanks.
Tom