sql server - What could be good ways to deploy ASP.Net Web Applications? -
we deploy web applications creating database , running sql scripts through query analyzer. copy output "publish website" , set website in iis.
we have seen websetup in visual studio, part seems thinly documented. example, not clear how ask user ip , password of sql server. tend websites deployed way coming under folders http://example.com/project, instead of http://example.com.
then there issues ajax.net not being installed or or other patch not applied.
so far, have physical access servers. pretty though going shipping cdroms. practical tradeoff between manual intervention , automation?
avoid visual studio deployment, , automate as possible. web deployment projects , nant can friends!
briefly, our deployment setup:
we use redgate sql script differences between dev , live database.
an nant build file calls msbuild build web deployment project (.wdproj), zips resulting compiled web app (along sql change script) , uploads zip file server.
on server side, there nant build file takes application offline, backs database, backs website. runs sql change script, unzips new version , brings app online.
step 3 run "manually" (one double-click), scheduled late @ night. same cdrom, or write pretty little windows forms app wrapper.
quite happy give details of nant script if you're interested.
Comments
Post a Comment