>I am using .Net 2005 and have developed two separate ASP.Net applications. One app using only SQL Server as a database and the other uses both SQL Server and Oracle. I have created both apps in their own projects. I have also created separate projects for my data classes and business classes.
>
>Also, I work for one company, so each project is somewhat related and will access each others data from time to time.
>
>My question is, should I create one solution in .Net and add each of these projects into the solution? Then modify and maintain each project through this one solution?
>
>I current will open multiple VS.Net sessions, one for each project, and switch back and forth.
>
>What is the better solution to managing multiple projects?
>
>Thanks,
>
>Jerry

The only difference that I can think of is if you have documentation files (Docs, Spreadsheets, etc.) and/or SSMS database projects that cover both projects then having them together in the same solution might make sense. You can add individual files like documents or an SSMS project file to a solution outside of a project. Also there is the memory overhead of two instances of VS.NET to consider.

Everything that I've worked with is oriented for the projects no matter which solution they are in. VSS and deployment packages are based on the project, not the solution. You can check in a solution to VSS but it is better to check in only the projects. Solutions under source control creates a lot of problems with multiple developers.