I'm coming up against the wall of VS 2005's limited "Web Deployment Project" capabilities. I like the unattended building and web.config replacement, but have several issues:
- Building over a VPN is slow as molasses. I have a single codebase that is replicated to multiple sites with merged site-specific configs. If I need to build two sites, it's 2X as slow. Clearly, this won't scale well. If I have 5 sites, I'd like to build once, copy 5x, and merge 5x.
- VS replaces the entire site rather than simply what's changed. As the scope of the app grows, again- scalability.
- VS won't update SQL schemas.
- To minimize production downtime, I'd like to have the site
built first, then assigned as the relevant path in IIS, rather than building directly to the production path. Currently, if my build dies (which can happen if my connection isn't perfect), the site is down while I do another build from scratch.
- VS won't do scheduled builds.
- There are times when I'd like to push out a build using multiple VSS branches, some of which don't require compilation. Basically, I have static assets like images in VSS but not in my VS.NET project because the consume a ton of build time and change very infrequently.
I realize I could script some of these together, but I'm not interested in duct tape. Does anyone have experience with
Visual Build Pro they'd like to comment on, or another tool? I'd like to cut out the VS.NET IDE from the process as much as possible.
posted by sandking at 7:14 PM on November 13, 2006