Best Practices - VSS integration with VS.NET, migrating our Classic ASP projects -- dotnet faqs

Keith A. Rowe
3/18/2004 11:53:38 AM

We currently have many Classic ASP projects that are stored in VSS 6.0c and
are maintained with VID 6.0. We have purchased VS.NET 2003 and know we need
to upgrade to VSS 6.0d if we want to integrate VS.NET with VSS.

We *eventually* want to convert the ClassicASP code to ASP.NET, but need to
run both environments side by side. We know we cannot easily share session
state between the two platforms, but want to co-mingle the two within the
same Virtual Directory. While this is possible is this recommended? Or
should we create all new ASP.NET pages in their own VD?

To recap, what are best practices for our situation? What is the best
stratey to make our Classic ASP projects available in VS.NET via VSS 6.0d?

Many thanks,

Keith

news.microsoft.com
5/3/2004 4:29:09 PM

Your classic ASP pages will be fine in shared directories, VS.NET 2K3 fully
supports classic asp, you will have no problems using both and switching
back and forth between the two.

If I were in that situation I would however use 2 separate projects in a
single solutions to easily accomodate users that need compatibility with 6c.

Oh yeah and becareful using VSS 6d w/ your vb5 com object (should you have
any) it can screw them up.

HTH

Nick Harris, MCSD
[quoted text, click to view]

dotnet faqs : Best Practices - VSS integration with VS.NET, migrating our Classic ASP projects