Single Project vs Many DLL's

[Sam Alex]

Hi,

We're working on a project with many modules, and we're trying to
determine how far to break down the components into DLL's. Can someone
give some pro's and con's on breaking out functionality into many DLL's
as opposed to only a few or even a single solution? This is for a Win
Forms app built in VB 2005 where the users will access it via Citrix or
Remote Desktop, so it will be deployed to one location.

Thanks --

Alex

[Michael C]

Re: Single Project vs Many DLL's

"Michael C" <mike@nospam.co mwrote in message
news:udQ9%23yGl IHA.1368@TK2MSF TNGP02.phx.gbl. ..

I don't think there is a question of whether a project should be broken
into components. I have done this and had great success. The only question
is how to break the project up.

I should add the I think the best way to break a project up is to put
specific functionality into different dlls. For example I have an app that
works with DirectShow, Twain and WIA. Each of these is a seperate dll,
although the GUI for each is in the main exe. That way if I start another
app that needs Twain then I just include the twain dll. I'm not a huge fan
of splitting different forms into different dlls as this can create a few
problems but I would do it as a last resort. Certainly I wouldn't start
splitting the forms into different dlls as the first option.

Michael