Shulou(Shulou.com)06/02 Report--

This article will explain in detail the error analysis of ASP.NET Web server configuration. The content of the article is of high quality, so the editor will share it for you as a reference. I hope you will have some understanding of the relevant knowledge after reading this article.

List by level, publish some configuration errors encountered by the client and server of the website. The writing is incomplete, because I don't think I have encountered the most serious mistake, or it is a kind of bug of the development tool itself. If this is the case, we will discuss it separately.

{error condition list:'1 is not a valid win32 application.' }

As a question of ASP.NET Web server configuration, the first thing I would like to introduce is your net framework-related questions. The environment on the server (Server environment) is consistent with the development environment, so on this basis, we can see whether the cpu of the server is x86 or x64, and follow the net framework executable component package on the server. IIS supports the asp.net program. To choose net framework is to decide which version of 1.x2.x3.x redistributable package to choose according to the operating system of different digits.

The second ASP.NET Web server configuration problem is that I encounter the most, the installation sequence of IIS and visual studio, which causes the trouble of whether you need to restart IIS after you deploy the website (I don't understand why, beg the expert to give me a point or two). The solution is also very simple: aspnet_regiis.exe-I.

The third ASP.NET Web server configuration problem that took me all morning to solve is the confusion of DLL dynamic libraries. The solution is simple: check the naming of all aspx and aspx.cs files and other pages for repetition. This problem is usually caused by copying the page and carelessly changing the naming. It's easier to modify.

Such a list is not very helpful for us to eliminate the problem of a train of thought, the idea is to determine our understanding of the problem, see that if there is still interest here, communicate with you, first talk about my solution.

Web.config customErrors mode = "true" display error

Try to see if html can access troubleshooting IIS issues

Database connection problems access other aspx pages (those that do not access the database) and eliminate the problem of connecting to the database.

This is the end of the error analysis on the configuration of the ASP.NET Web server. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.