Three Tier Web Project Structure

[Glenn Whyman]

Hi,

We've recently completed the design for a three tier web application and are
about to commence development.

When building and deploying is it better to have a VS.NET project for each
logical tier and another for 'Utility' classes. That is each project will
only contain classes for a particular tier, and each tier will compile into
a different assembly. As opposed to compiling the entire application into a
single assembly.

Thanks for the feedback,

GB

[Klaus H. Probst]

There's no One True Way for doing this. You definitely want to physically
separate your code in functional areas and separate assemblies, but
ultimately you want to use an approach that fits *your* project. Certainly
using a DLL/project for each tier is a good start.
--
____________________
Klaus H. Probst, MVP
http://www.vbbox.com/

"Glenn Whyman" <gw*****@evaluationsolutions.com> wrote in message
news:es****************@TK2MSFTNGP10.phx.gbl...

Hi,

We've recently completed the design for a three tier web application and are about to commence development.

When building and deploying is it better to have a VS.NET project for each
logical tier and another for 'Utility' classes. That is each project will
only contain classes for a particular tier, and each tier will compile into a different assembly. As opposed to compiling the entire application into a single assembly.

Thanks for the feedback,

GB