What is the correct way to make changes to an ASP.NET project?

V

voronin_denis2016-11-23 17:31:35

IIS

voronin_denis, 2016-11-23 17:31:35

There is a test and deployed project on ASP.net. How to correctly make changes to a project deployed on IIS. Tell me, maybe there are deployment docks for making changes to ASP.net MVC projects. In VS, it is possible to deploy a project if it is accessed locally. But what if there is no direct access. FTP only

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

V

Vladimir Bondarev, 2016-12-02
@voronin_denis

The "Publish" function in VS is just a delivery detail. Form a delivery package and deploy it to FTP.
Substituting files, whether binary or text, is a bad practice, you can break something off and then suffer for a long time restoring the previous state. Each delivery contains changes, which means that a version that contains a certain changelog must be assigned, otherwise mess will begin after a series of such deliveries.
I will describe the general delivery process:
This is a process that we did not arrive at immediately. There were file substitutions in production and live editing of the code. Sometimes this led to disastrous consequences. Then a manual delivery procedure was iteratively developed, after which this procedure was automated to save time. Currently, the longest delivery phase is manual acceptance testing on a demo environment. There are also automated acceptance tests - they are run after the build is assembled, but like all code, they may contain errors, so we do not dare to exclude manual testing of acceptance tests.

P

Peter, 2016-11-23
@petermzg

In Visual Studio there is a button "Publish ..." and you can either deploy directly to the server by IP address or create a zip package, which can then be deployed from IIS Manager.

R

Roman, 2016-11-23
@yarosroman

Your project is compiled into a DLL, if you have changed something in the controllers, it is enough to replace the DLL, if in Razor Views, then it is enough to replace them. It is advisable, of course, to stop the site / server, and do a full update, because you may have updated some of the packages used in the project, and they are not compatible with older versions.