Structure for extremely large multi-tier Web projects

[Dan Munk]

Hello,

I am working on a very large multi-tier Web application. The
application consists of approximately 100 middle-tier/back-end projects
and 200-300 presentation projects. Obviously this is too large to
manage in a single solution. The development staff have each developed
ways to work within such a behemoth structure, but we have not been
able to come up with a standard for project-to-solution organization
and how to manage dependencies across them.

As we work on our migration to 2.0 I would like to clean up and
standardize our projects and solutions. Has anyone tackled a similar
issue with success? Is it reasonable to try and keep management of
this within Visual Studio or is an external build tool a better option?
If an external build tool is used have people found it difficult to
keep the Visual Studio environment in sync?

Any thoughts or opinions would be a big help.

Thanks,
Dan

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Well that's a huge project indeed, what it's about , if I may ask?

Take a look at RUP (Rational Unified Process) it's intended to be used in
large projects as this one.

 

[Dan Munk]

It is software for government bodies. I agree that RUP is applicable,
however I am wondering more about the physical layout and structure of
projects, the solutions that contain them and how to manage the
dependencies between them.

Thanks
Dan

 

[Guest]

Maybe I am stating the obvious and you are already using it, or have
considered it, but this sounds like a job for Visual Studio Team Edition with
Team Server.