Incrementally updating a asp.net web site? -
Is a good way to make incremental changes to ASP.NET.net website without re-publishing the entire site?
I am taking an old website from classic ASP to asp.net, and one of the things happening on the site is being converted into isolation. The site is only on one server, and there are several files so that one will reproduce the entire site down for some time. I would like to avoid it, or at least as low as that time.
Every page has a code on the back of the file, and some pages are used by each page in the appboard (just in that case if you are building a web site (a web application's Instead, where).
All code is compiled in .dll in the /. Folder), And it seems that you can actually deploy only those files that have changed to server - numRecompilesBefor EAppRestart
machine or web In config files - this is missed for 15.
If you apply any changes in the / app_code
folder, then it will recompile the site as it is a shared area.
One thing: VS2008 and below, the published site command will publish the entire site - I believe it is much better in VS2010, where it is easy to publish, just replace files - then This will require you to manually deploy the changes.
Comments
Post a Comment