What is the best practice for uploading a .Net project to a server without disrupting users?
Visual Studio has a Publish button that allows you to upload via FTP. I noticed that when you publish, there is downtime (when critical files such as DLLs are overwritten). If something doesnβt work, how do I roll back?
How do I do version control so that I can revert to a previous implementation?
Thanks y'all.
Publish to local IIS.
IIS 7 " ", . , IIS 7, -. " ". . , .
IIS 6 . .
Source Safe/ Team Foundation Server, , , "1.4.2343" . . [ + ]. :).
.
:
, . ( ).
" /" .
, .
"Maintinance" , .
FTP- .
....... .
,
Source: https://habr.com/ru/post/1772954/More articles:copy production database to capistrano stage - ruby-on-railsWhy does setting a default make this function private? - closureshttps://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1772951/alternatives-to-jpegreadheader-libjpeg&usg=ALkJrhhtyQ_jq3tJfQZFrba7VtHULYXFOQC ++ private constructors - c ++Usefulness of loading instances in OO PHP? - objectWhat is the difference between "$ .FunctionName ()" and "FunctionName ()"? - javascriptWhen I click, I want to add the value of the a-tag to the input field - javascriptsingle quote in file name - javascript, php - javascriptfind all rows in a list containing x or y? - listSet thread volume ALSA - linuxAll Articles