G
Guest
I would like to solicit advice on how to best deploy an enterprise ASP.NET
2.0 web application. I'm using VS 2005 and I've found Publish Web Site to be
somewhat lacking, buggy, and slow.
My application consists of 250+ (and growing daily) ASP.NET files that I'm
compiling into separate binaries (all stored in /bin). The ASP.NET front-end
files are stored in 10 different directories (and growing).
My current method of development for fixing bugs or adding new features is
as follows:
1. Fix bug or add feature request locally.
2. Compile site.
3. Manually FTP all files and binaries, directory-by-directory. (Since
compiling to binary always updates the time/date stamp, it's impossible to
transfer just those files that have changed since last compile).
4. Test in beta environment.
5. If successful, FTP to production site manually. If not, repeat above
until ready for production.
As you can imagine, this is an extremely time-consuming process. It's not
agile, nor automated and prone to keeping me working later than I'd like.
Any suggestions that you could offer in expediting deployment, especially
based on your experience, would be greatly appreciated.
Thanks in advance.
-Brenden
2.0 web application. I'm using VS 2005 and I've found Publish Web Site to be
somewhat lacking, buggy, and slow.
My application consists of 250+ (and growing daily) ASP.NET files that I'm
compiling into separate binaries (all stored in /bin). The ASP.NET front-end
files are stored in 10 different directories (and growing).
My current method of development for fixing bugs or adding new features is
as follows:
1. Fix bug or add feature request locally.
2. Compile site.
3. Manually FTP all files and binaries, directory-by-directory. (Since
compiling to binary always updates the time/date stamp, it's impossible to
transfer just those files that have changed since last compile).
4. Test in beta environment.
5. If successful, FTP to production site manually. If not, repeat above
until ready for production.
As you can imagine, this is an extremely time-consuming process. It's not
agile, nor automated and prone to keeping me working later than I'd like.
Any suggestions that you could offer in expediting deployment, especially
based on your experience, would be greatly appreciated.
Thanks in advance.
-Brenden