Like many Microsoft developers, I've used VSS as my primary source control system - and suffered for it. Perhaps the biggest problem I've had with VSS is the inability to batch the creation of ASP.Net web projects. Such applications require a virtual directory, and it seems like VSS hard-codes this info into a binary (not even an XML file) somewhere.
Automating Web project creation is useful for improving process. For example, you could create a batch script that get a version (whether the latest of a branch) from source control, and does all the preparation work to make it ready for development (set config values, create its own databases, make the virtual directories, etc...)
Normally to automate ASP.Net app creation (which I'll discuss more in another blog), you need to:
- Get the source code
- Create the virtual directory in IIS (with VBS, Directory Services, or even NAnt's
- Set the virtual directory in the *.webinfo file
- Set the virtual directory in the solution file
The problem becomes when VSS is tightly integrated into Visual Studio, then it creates a fifth step:
- Find that binary file, "decode" it, set the virtual directory, and recode.
After *hours* of looking at this, I finally had to move onto other things.
However, my new firm (Ameripay) uses non-VSS source control that isn't tightly integrated into VS.Net, so it doesn't have that limiting 5th step. Consequently, I can now automate the creation of Web projects.
Post a Comment