ASP. NET night talk

(P14)
If the Cookie is enabled on the client, the SessionID value is transmitted between the client and the server through the Cookie;
If the Cookie is not enabled on the client, the SessionID value is passed through the URL;

(P15)
Session data is stored on the server;
The Session can store any type of data (Object type );
The default life cycle of a Session is 20 minutes. You can manually set a longer or shorter time;

(P15)
The Cookie is stored on the client rather than on the server. Each time the client sends a request, the Cookie will be sent to the server together. Each time the server responds to the client request, the Cookie will be sent to the client again for storage;

(P20) <% = %> is used to output the variable value to the output stream;

(P22) in ASP. NET, a root directory operator (~) that can only be used on server controls or server code is introduced (~), It indicates the root directory of the current application;

(P24)
The parameter names and parameter values are displayed in the address bar of the form submitted in the GET method. The POST method does not. The parameters submitted in the post method are more concealed and secure;

Because there is a limit on the maximum number of characters that can be entered in the address bar of the browser, you cannot use the GET method to submit a form with a larger parameter value, but the POST method does not;

(P25)
Common methods to obtain HTML control values:

Request. QueryString ["Control name"] -- suitable for forms submitted in GET mode;
Request. Form ["Control name"] -- Form suitable for POST submission;
Request ["Control name"] -- form suitable for both GET and POST submission;

(P28)
In the form on the server side, you do not need to specify the action attribute to indicate that the current page is used for processing. You can also choose not to specify the method attribute. By default, the form is submitted in POST mode;

An ASP. NET page can have only one server form, and the ID value of the control in the server form must be unique;

(P74)
Button Click events and Command events cannot be used at the same time. If you need event data, use the Command event and set the CommandEventAgrs attribute to include event data. If you do not care about event data, you can simply use the Click event;

(P101)
The DataReader object cannot be directly instantiated and must be created using the relevant Command object;

(P116)
After the DataSource attribute or performanceid attribute of the data binding control is specified, the bound data is displayed only when the DataBind () method is called;

DataSource and performanceid attributes cannot be used at the same time;

The DataSource attribute of the data binding control must be an enumerated data source, for example, an instance that implements the class of the ICollection, IEnumerable, or IListSource interface;

(P120)
You can access the attributes, variables, or methods with return values of the class corresponding to the current page within the <% # And %> delimiters, the premise is that the access control operator for attributes, variables, or methods with return values must be protected or public;

XML data sources must use the XPath function when binding to a data binding control. Other data sources must use the Eval or Bind function when binding to a data control;

(P198)
<ConfigSections> the node specifies the configuration section and handler declaration. If the configuration file contains <configSections> nodes, the <configSections> node must be the first subnode of the <configuration> node;

(P255)
The ScriptManager control can only have one control on the page, and must be located before all the server controls on the page;

The ScriptManager control has an important attribute EnablePartialRendering. The default value of this attribute is true, indicating asynchronous refresh. If it is set to false, it is no different from the traditional ASP. NET page;

(P288) to avoid SQL injection, we recommend that you use parameterized SQL statements or stored procedures to access the database;

(P363) The FileInfo class provides two methods for reading/writing files: byte-based and character-based;

(P369)

There are two types of streams in. Net: byte-based and character-based;

A byte-based Stream abstract class is defined in. Net. This class is a Stream class. All non-abstract classes based on byte streams are derived classes of the Stream class;

(P373) the classes that perform read operations in character-based mode are all derived classes of the abstract class System. IO. TextReader;

(P374) classes that perform write operations in character-based mode are all derived classes of the abstract class System. IO. TextWriter;

(P377)

The so-called encoding refers to the process of converting Unicode characters into a byte sequence; the so-called decoding refers to a reverse operation process, which converts the encoding byte sequence into a Unicode character;

The. Net Framework provides an Encoding abstract class Encoding, which is located in the namespace of System. Text;

This article is from the "Richard-Tian" blog, please be sure to keep this source http://tianjing.blog.51cto.com/5172108/1238886