The original Rich control is a class name, not a specific control.
* Rich control: Generate calendar, file upload button, and alternate display... Meaning of such controls
(I have 691 pages on the volume... Cry ~ Shuang ~)
* Runat = "server": I have never understood it, because sometimes I need html controls, but asp.net controls are not what I want to generate, however, html controls have no service features. As you can see, simply add the runat = "server" attribute. It's so nice.
* Event generation: md is really nice. It takes only two minutes for a great place. Originally, the two boxes on the top of my first class only noticed its role when I wrote the class, I didn't expect that the new controls would also be available, but this is the case. I am not careful enough, haha. However, it seems that my 08 was unresponsive and dizzy.
* Trace: In the page definition, trace = "true" is cool. md has always known that many people use this method to view the page status. It is so cool to develop this habit today. Pai_^
* ViewState: Previously, the server manually erased the original record (such as ErrorMessage). Disabling vs seems easier and better.
* ControlState: only records the status information of the current control, such as the selected row information of the gridview.
*. NET file path :?? \ Windows \ Microsoft. NET \ Framework \ [Version] \
* Temporary ASP. NET Files: a folder in the directory above, used to store compiled page classes. Each page is a class. If it is the first access, it is compiled and stored here. (^ _ ^, Or the embodiment of the temporary stick-up principle, haha), of course, the class here is automatically generated. net maintenance, it should be iis (guess), so it will always be synchronized to the latest class. By the way, do not forget to clear the browser cache ^_^ during testing.
* ComplationMode: This page can be disabled when it is set to Never. It is easy to think of static pages. Yes, this page can be disabled if it is set to Never.
* # Line: Define the row forcibly and overwrite the original row. For more information, see msdn.
* FindContral (): it is convenient to use when the ID is not referenced.
* Control tree: the entire page is a tree, and the root is the class of the current page.
* Code hiding: select the check box when creating the file: place the code in a separate file. In fact, we generally use this double file method.
* Presentation Page: displays the. asp Page with no code.
* Double file structure (code hidden structure): three classes are generated. Originally, one class is perfect (partial classification), but it is to support asp. because of the advanced attributes of net1.X, this complex structure is available. Page A generation: A.1 (one partial category), a: A (used to present the Page), A.2: Page (one partial category), and A is generated twice, a is generated when a request arrives (A.1 is generated at this time, and A.2 is generated );
* The Load and PreRender events are different: the load events are automatically generated by default, but like the problem I encountered last time, they occur before the control event, the prerender occurs after the control event.
* AutoEventWireUp: automatically registers events, but not all page events, such as InitComplete.
* Trace. axd: You can view the last 10 traces through Assembly requests. You must set <trace enabled = "true" localOnly = "false"/>. The attributes writeToDiagnosticsTrace and mostRecent are both excellent.
Chapter 1 ends here, page 36