Introduction to ASP. NET Website Design Requirements

ASP. NET Website design requirements-website file name:

1. The website file name describes the business content in standard English words. If one English word cannot be described, you can add two or three words, but try to use them as full words, such as article. aspx/articleView. aspx/articleList. aspx.

2. Do not use numbers to describe the file name.

3. The file name should not be too long. It should be up to 20 letters.

4. The image file name should describe the image content category as much as possible. Use btn, menu, title, arrow, line, dotline, bg, and other prefixes as much as possible. For example:

Btn_friendlinks.gif/title_contactus.gif

5. Do not use. inc or other names for include files. This file name can be downloaded, which is not safe. All files with dynamic content must adopt

Development Technology name. For example, dbconn. inc. aspx/index. lang. aspx.

6. Try not to generate files of the same name in different folders. For example: modules/index. aspxlanguage/index. aspx

ASP. NET Website design requirements for designers:

1. Save the image file. After cutting the image, the website page designer classifies the image and places the image with text in the language/images/folder. Put images without text in the templates/current website name/images/folder.

2. Save the CSS style file. The website has at least two CSS files, one of which is the language/The langstyle.css file. This css file defines the text size and font after the language conversion. In addition, the css file is saved in the templates/current website name/styles folder, which is used for page layout display.

3. Save the Media file. Common media files such as Swf files can be stored in the same way as image files. However, it must be divided into text and text.

4. Save page files. All page files are stored in the templates/current website name/directory, regardless of subdirectories. The file extension is. HTML or. tpl. aspx/. tpl. php. The link is either absolute or relative, and cannot be mixed.

5. The file name is named according to the second description, and files such as inc do not need to be extracted. If the designer modifies the public part, specify the document to use.

Requirements for programmers in ASP. NET Website Design:

1. Modular programming with hierarchical development of display layer, control layer, and data layer. Reusability is considered during module design to facilitate application to other projects.

2. class-based programming increases code reusability and readability.

3. Clear comments to facilitate subsequent modifications by developers.

4. the HTML template reading, control module classification, and data operations should be clear and not obfuscated.

5. Based on Multi-language and multi-template development ideas, it facilitates website upgrade, revision, function expansion and transplantation.

ASP. NET Website design requirements-other instructions:

1. The website background management function is also applicable to the above architecture. Of course, you can cancel the template function design section.

2. HTML's affinity Design for search engines, DIV + CSS layout design, is to look at the integrated skills of designers.

3. Programmers consider the security of interactive content transmission. You can use SSL technology to encrypt and transmit sensitive data, or use Javascript encryption + background script decryption to send and receive encrypted data in the form of an exchange key. This solution is cost-effective and fast.

4. Programmers prevent SQL injection attacks, brute-force Code cracking, and upload vulnerability detection.

5. Application of Technology hiding and URLRewrite. Development and deployment of the URLRewrite application or hidden extension under IIS.

6. The output of this architecture is based on functional actions instead of page access. For example, you can directly access/member/infoModify. aspx before accessing the member information. And the architecture is through/cmd? Act = memberModify access.

7. Differences between the Components directory and the Modules directory. The Components component directory usually stores completely independent functional Components that are completely portable, such as vote Voting, counts statistics, editor General HTML editor, and so on. While most of the Modules are website service layers, which have poor portability and are equivalent to website columns, and feature discretization is complicated. It can also be understood as developing components that are compatible with various websites. modules must be independent business logic services.

1. Shell functions in ASP. NET Environment
2. Batch insert data to databases in ASP. NET
3. ASP. NET sends data to webpages in Post Mode
4. WEB Application Deployment in ASP. NET 2.0
5. HttpWorkerRequest object in ASP. NET
6. Eve of the owc component in ASP. NET 2.0