Recommended: Location of the "Web Anonymous User" account password Q: We want to grant access to the Web anonymous user account to read information from other systems; however, we do not know the password for that account. How can I get this password? Answer: IUSR_<computer name> The account is Web anonymous
In the process of technological updates, there are still some people who hold on to things that are already out of breath. Some people, although they have entered a new world, still cannot get rid of the old habits. I did not use the word bad habits because I am also very disgusted with this word.
New technologies should have new technologies. When entering the world of ASP.NET, you should correct your past habits, enter a new world, and throw away the junk of ASP.
The following lists are all wrong practices, please do not mistakenly think that it is a recommended practice and promote it:
1. Use server side include to introduce common page composition to ASPX.
Under the ASP.NET mechanism, ASCX (web user control) should be implemented. ASCX provides more controllable interfaces. And more importantly, ASCX is a class. A tangible class can fully control it.
2. Do not use web.config
web.config provides a very rich configuration management interface. It is the core part of an application. However, many people's web.config is often empty. Or it has never been modified.
3. Use Response.Write to output messages to the front end
Response under the ASP.NET platform is very different from Response of ASP.NET. Although it means the same meaning, its usage is very different. The content of Response.Write will only be output to the front end of the page. The correct way to output messages to the front end is to use PlaceHolder.
4. Use a series of sessions to manage user connection status
This method is abused in ASP. In the ASP.NET environment, the correct approach should be to design a class, save data structured, and encapsulate access to sessions or cookies.
5. Use session to verify identity
This is almost a common problem. ASP.NET provides a set of APIs for user authentication. The types are form verification or windows verification. There is a section on Quick Start that explains this very clearly. Most people can still rely on assigning values to the session to maintain user authentication status.
6. Redirect pages using Response.Redirect
This can be used when necessary. But it cannot be abused. It turns out that abuse of redirection will cause serious logical confusion. This is what you do when using pages as program units. Using front controller mode will make the user's operation logic centralized]
7. Use too many ASPX pages
The program units in the ASP environment are only *.asp pages, and ASP.NET is not the case, as well as back-end class libraries, ASCX, etc. Business logic should be concentrated in different units, rather than using one ASPX for one operation. More often, ASPX will manage in-page logic as a container for ASCX or custom control. While ASPX reuses ASCX, ASPX is also reused as a unified page composition.
8. Copy code between multiple logical units and modify the corresponding logic
Reuse. Reuse. Reuse. The principle of dealing with such problems is to not have any same or similar processes. If you use the above method, once there are major logical changes, the results will be disastrous.
Share: ASP code: rs.open statement detailed description The following is the referenced content: '*********************************************************'rs.open statement details 'rs.Open [first parameter],
2 pages in total Previous page 12 Next page