To Gui.dll or not to Gui.dll

[=?Utf-8?B?bl9sbG95ZA==?=]

Hi all,

I'm designing a Winforms application. I'd like to know if people would
recommend placing all the Windows forms for the application in a DLL i.e.
GUI.dll or break down the 'modules' of the application and place the win
forms into each module/dll. For example if I have a custom word processor,
would the recommendation be to place these forms into the GUI.dll or create a
DLL called WordProcessor and place the forms for the word processor into it?

I know that reuse may be reduced somewhat by placing the forms into the
word processor dll, but could I make the assumption that these specific forms
might not be accessed from anywhere else but the word processor? And where
can the line be drawn between reuse and 'component' based development?

Regards.

[Kevin Spencer]

Any coponent you might re-use in another application would be useful in a
DLL.

--
HTH,

Kevin Spencer
Microsoft MVP
Software Composer
http://unclechutney.blogspot.com

I had the same problem once. Fixed it using the same solution.

"n_lloyd" <nl****@discussions.microsoft.comwrote in message
news:73**********************************@microsof t.com...

Hi all,

I'm designing a Winforms application. I'd like to know if people would
recommend placing all the Windows forms for the application in a DLL i.e.
GUI.dll or break down the 'modules' of the application and place the win
forms into each module/dll. For example if I have a custom word processor,
would the recommendation be to place these forms into the GUI.dll or
create a
DLL called WordProcessor and place the forms for the word processor into
it?

I know that reuse may be reduced somewhat by placing the forms into the
word processor dll, but could I make the assumption that these specific
forms
might not be accessed from anywhere else but the word processor? And where
can the line be drawn between reuse and 'component' based development?

Regards.