Chapter 3 When you create a new solution, you can select the established location. By default, you can choose the IIS, FTP or Remote's Web by operation.
Site on site. When adding an item, you can choose whether to put the Presentation Code and Logic Code in a file. Many MasterPage and Previouspage PAGE, followed by adding a lot of Controls, such as Navigation, and more events for Personlize (WebPart, Webzone, WebPartManager), now Page executes: Preinit, Init , INITCOMPLETE, PRELOAD, LOAD, LOADCOMPLETE, PRERENDER,
PrerenderComplete PreviOUSPage is used for Cross-Page Posting, and cross-page posting is the POST action, not sending back this page, but another URL page, such as below
Code
Page2's BEHIND CODE is incorporated to call the POST action source Page1.ASPX's Controls. Access to Control on Control on page1.aspx, one is Page1.aspx announcement
Property, the other is previouspage.FindControl (ControlID), where controlId is a string. Forgot to say, PreviOUSPAGE definition is to use
Directive is defined, for example, in Page2.aspx <% @ previousPageType VirtualPath = "~ / default3.aspx"%>. At the same time, use newly added attributes
ISCROSSPAGEPOSTBACK can intercept the Cross-Post. About folder. In ASP.NET 2.0, by using predefined folders, IDE will automatically compile programs for programmers. MMD, don't understand, don't know the right to translation. / Code folder, storage class, .wsdl file, type DataSet, if you put a .cs file in the Code folder, VS automatically compiles it, put it into a .wsdl file, VS
Create a web service's proxy class, put it into a .xsd file, VS automatically creates a type DataSet, as long as these automatic creation is complete, all the same SOLUTION will immediately call these items. Steps to implement the Code folder: Create a folder, named Code, VS will handle it, at least icon is different. If it is a multi-developed language, you can build
Those note, and in the web.config file, the example is as follows:
/ Themes folder, stores .css file and server control by image
/ Resources folder, in VS 2003, if you want to make globalization and localization, you need a resgeN.exe tool, now in vs2005, no, put the RESX file directly
Of the resources folder, you can
Compilation, compile, when Page is first browsed, the request is sent to the ASP.NET Analyzer, the ASP.NET Analyzer creates a class file, and then the class file is compiled.
DLL, write to the hard disk of the web server, then response this class file; when requesting this page, Request is just a simple instantiation of the DLL that has been created.
And returning it to the request is OK. But it is also this mechanism, so that if there is a little change, it needs to recompile the program. I am very annoying that in VS2005, it has improved, this compilation is called in-place
PreCompilation, the specific approach is to replace the name of Page with precompile.axd, such as http: // localhost: 8080 / MyWebsite / Aaa.aspx in IE
Address bar more http: // localhost: 8080 / MyWebsite / Precompile.axd
Data operation: In VS2003, it is very complicated DataAdapter, Dataset, and finally performs DataSource settings. It is very troublesome, now VS2005 simplifies these, give a few
DataSource, such as SQLDataSource, which connects SQL, connect AccessDataSource, and more. GridView, display data, DataSourceId, DataSource connection, allowpaging allows paging, and allowsorting allows sorting,
