As far as VS 2005 or VS 2008 are concerned, “Classic ASP” applications are just text files. You can edit them and you can check them in and out of version control. When people ask about managing “Classic ASP” applications with VSTS/TFS, they’re usually asking about how they should manage the VB6 components. Here’s what I recommend for VSTS/TFS 2008:
<?xml version="1.0" encoding="utf-8"?>
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" />
<VB6>$(ProgramFiles)\Microsoft Visual Studio\VB98\VB6.exe</VB6>
<Message Text="CompileProject: %(ProjectToBuild.Identity)"/>
<MakeDir Directories="$(VB6Output)" Condition="!Exists('$(VB6Output)')"/>
<Exec Condition=" '@(ProjectToBuild)'!='' "
Command=""$(VB6)" /m "%(ProjectToBuild.Identity)" /outdir "$(VB6Output)" /out "$(VB6Output)VB6.log""
Thanks to Martin Woodward (Team System MVP) of Teamprise (provider of cross-platform TFS clients) for his suggestions to include the import of the Team Build targets file and to override the AfterCompile target. Of course, you can customize your project file as necessary to meet your requirements. Be sure to check out the MSBuild Extension Pack, Microsoft SDC Tasks, and the MSBuild Community Tasks Project for a number of helpful custom MSBuild tasks.
Create a new build definition and, on the Project File page, browse to the TFSBuild.proj file you just checked into version control.
That should put you well on your way towards building a “Classic ASP” application with VSTS/TFS 2008. Please let me know if you have any questions.
Note: I used an Online HTML escape tool to escape the project file snippet and Google Prettify to do the syntax highlighting.