What's the standard practice for compiling .net web applications through the source control process?
In the ASP days, we used shadow folders to serve as the source for staging websites. With compilation of .net today, what is the standard practice? Run everything with codebehinds until production and then use aspnet_compiler.exe?
cheers,
a
Shadow Folders and compiling ASP.NET Web Apps
Moderator: SourceGear
-
- Posts: 1
- Joined: Fri Jun 08, 2007 4:50 pm
abbie:
You can choose a number of different development styles to solve this problem. Personally, I like the model of an isolated development environment against a local web server, and then deploying from our build system.
A good reference on this would be Microsoft's Team Development Document. Just substitute Vault for the version control tool.
You can choose a number of different development styles to solve this problem. Personally, I like the model of an isolated development environment against a local web server, and then deploying from our build system.
A good reference on this would be Microsoft's Team Development Document. Just substitute Vault for the version control tool.
Jeff Clausius
SourceGear
SourceGear