N-tier single project or multiple projects?

[kamere]

For your N-tier solutions. Have you architected your UI, Business, and
DAL layers into one single project or have you separated them out into
separate projects? What would be the benefits of having all 3 layers
in one project vs breaking them out to there own separate projects?

 

[Michael Nemtsev]

Hello kamere,

the reason is to give flexebility to your solution. one solution, several
projects for each layer. It's MS guideline.
They even supply an enterprise project template for VS, where you have several
template projects for each layer

k> For your N-tier solutions. Have you architected your UI, Business,
k> and DAL layers into one single project or have you separated them out
k> into separate projects? What would be the benefits of having all 3
k> layers in one project vs breaking them out to there own separate
k> projects?
k>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

 

[Guest]

The obvious advantage (to me, at least) is that if I intend to use one or
more in another application, I can add it's project to my new Solution
without having to cannibalize it out of the original one.
Peter

 

[Andy]

I'd go with seperate projects, because you'll end up with seperate
assemblies. Once you have seperate assemblies, you can physically
split the layers of yur application across machines.

Check out Rockford Lhotka's Expert C# Business Objects (there's a
VB.Net version of the book as well, and he's releasing updated books to
take advantage of .Net 2.0). He goes into exactly this (all layers
can be on one machine, or split among multiple).


HTH
Andy