Srinudotnet

Hi,

I have a web application which uses both Legacy(Asp) website and Asp.Net(Framework 1.1) web application, both were using VSS 6.0. Currntly we are requested to define best VSS strucure by integrating both Legasy & Asp.Net applications under VSS 2005, nothing but upgrading from VSS 6.0 to VSS 2005.

My request is to, are there any best practices for define some best VSS structure in VSS 2005 and how to integrate Legacy(Asp webstie) & Asp.Net(Framework 1.1) web applications into a single VSS 2005 Database.

Thanks in Advance.

Srinivas




Re: Visual Studio Source Control and SourceSafe Integrating Leagacy Asp and Asp.Net(Framework 1.1) applications into VSS 2005

Richard Berg MSFT

ASP and ASP.Net are different enough that branching & merging between them would probably not be useful. I'd just add them as separate folders (or "projects" as they're called in VSS).

There is no difference in the VSS 2005 database format so you can use the same process from 6.0.





Re: Visual Studio Source Control and SourceSafe Integrating Leagacy Asp and Asp.Net(Framework 1.1) applications into VSS 2005

Srinudotnet

Hi Richard,

Thanks for your response, i still have some doubts about Migrating Legacy Asp & .Net Web application in to VSS 2005.

Yes, as you said it is better to manage both as separate projects or folders under a VSS Database.

are there any best practices defined my microsoft or any help to define a better folder structure in order to achive

"Release Oriented Projects to VSS for applications that utilize ASP/COM+ and .NET technologies".

My main concern is how to define a best folder structure to the applications which are using both legacy asp & .Net applications for VSS 2005.

Kindly let me know how to complete these tasks in a better way.

Thanks

Srinivas






Re: Visual Studio Source Control and SourceSafe Integrating Leagacy Asp and Asp.Net(Framework 1.1) applications into VSS 2005

Richard Berg MSFT

The precise folder structure doesn't matter too much, so long as you make sure that relative paths are kept constant. That's the best way to ensure everyone can sync & build the code without special working folder mappings.