Common Mistakes in Asp.net web project deployment

In the long-term development of Asp.net projects, it is very common to deploy web projects. Then there is a lot of common thingsProgramDevelopers and even programmers who have been developing for many years will encounter some mistakes that should not be made during deployment:

Error 1: after the development of the Asp.net project is completed, the compiled DLL is directly deployed when debug debugging is used.

Correct practice: Upload the DLL file after the Asp.net project is compiled in release mode, which is more concise and effective than the DLL file generated in debug mode.

Error 2: When the WEB Project is deployed on the server, set the debug option of compilation in the web. config file to true.

Correct practice: Set compilation debug to false during deployment. In this case, the. NET program will respond much faster during running than when debug is set to true.

Error 3: directly deliver the error prompt to the customer without any processing. In Asp.net, we often use try catch finally to catch exceptions, while web. the default setting of the error prompt in config is: <customerrors mode = "off"/>. We 'd better set it to remoteonly. In addition, it is best to make some corresponding errors into the corresponding error response page. In addition, you can add a link to the error page and return it to the Home Page. In this way, the user experience will be much better.