Understanding Solutions and Projects

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

We have a web site (intranet) that was created in VS 2003. The site is made
up of mulitple projects. In VS 2003 we setup each part of the website as its
own project/solution. In short we have a main root directory where the main
website stuff is, then we have sub webs that contain parts/portions of our
website. Every subweb is its own solution project, with its own setup.

We have recently started upgrading to VS 2005 and I am wondering if we
should change how we have this setup. Is it common to have 1 solution and to
include all of the projects (sub webs) within that solution. Is there a guide
on how to move the projects into one solution (keeping the directory
integrity, etc)? If so, then do we create 1 deployemnt msi to install the
entire website eveytime we have a change?

I was just wondering what is common.

Thank you,

[sloan]

Make sure you get VS2005 SP1 ~before upgrading.

Then give it a shot.
"Lyners" <Ly****@discussions.microsoft.comwrote in message
news:55**********************************@microsof t.com...

We have a web site (intranet) that was created in VS 2003. The site is
made
up of mulitple projects. In VS 2003 we setup each part of the website as
its
own project/solution. In short we have a main root directory where the
main
website stuff is, then we have sub webs that contain parts/portions of our
website. Every subweb is its own solution project, with its own setup.

We have recently started upgrading to VS 2005 and I am wondering if we
should change how we have this setup. Is it common to have 1 solution and
to
include all of the projects (sub webs) within that solution. Is there a
guide
on how to move the projects into one solution (keeping the directory
integrity, etc)? If so, then do we create 1 deployemnt msi to install the
entire website eveytime we have a change?

I was just wondering what is common.

Thank you,