Introduction to new features of ASP. net4.0

ASP. net4.0 has been around for a long time, but I am still learning and using 2.0 as a project. In order not to be too short-sighted, I read several articles about 4.0 Article . Now let's take a note to get started. If you want to use each new feature in depth in the future, it is best to use it ^_^.
1, Control Viewstate -- Now the default value of enableviewstate is true. Many developers rarely set it to false even if we don't need it, I will also review this point). A large part of Asp.net resources are wasted on this. In 4.0, the default enableviewstate is false, which also increases developers' requirements in disguise, because developers must know which viewstates need to be set to true.
The original English text is like this:
Control over view State -- currently, view State is enabled for all controls by default. most developers are pretty lazy about disabling view State when they don't need it. in ASP. net web forms 4.0, You can invert the normal state of things and disable view State by default.
2,Control client IDS -- This feature greatly reduces the client workload. You can generate HTML tags on the server using JavaScript and CSS. For many developers engaged in Asp.net, JS operations on server controls are quite uncomfortable (compared with JSP and PHP, or Asp.net is criticized as a short board ), it is estimated that Ms was finally compromised by the voices of the masses. With 4.0, getting the Server Control ID is as easy as other dynamic page technologies (forget the annoying binding and clientid to get the DOM element ID ).
Original English:
Control over client IDs -- this is a welcome feature for those of us who do a lot of client-side programming.
This change will make it much easier to target HTML tags rendered by server-side controls with JavaScript
And Cascading Style Sheets.
3, Better support for Web Development Standards -- This estimation MS is also in line with the trend. IE7 and 8 are all designed to move closer to the Web standard. However, Ms still has many of its own standards, so it is difficult to say "better support" instead of "completely compatible.
Original English:
Better support for web standards -- several improvements have been made to the ASP. net web forms 4.0 framework that enable you to more easily build websites that are compliant with web standards such as XHTML and accessibility standards. for example, you can prevent a formview control from rendering an HTML table automatically.
4. queryextender control-every time Ms comes new things, it seems that Program Personnel become more silly innovation. The new queryextender control makes it easier for you to filter data and retrieve entitydatasource or linqdatasource. It is no longer easy for developers who drag controls.
Original English:
Queryextender control -- The New queryextender control enables you to easily filter data retrieved
The entitydatasource or linqdatasource controls. You can use it to easily create search pages.
5. Search Engine Optimization (SEO)-a more friendly URLs makes it easier for search engines to index your web pages.
Original English:
Search engine optimization (SEO) -- there are several new features added to the ASP. NET Framework
That make it easier to get your website pages indexed by search engines. For example, the new ASP. NET web forms routing framework enables you to expose your ASP. NET pages with more intuitive URLs.
6. Improvements to dynamic data-entity templates enable you to create templates for display, modification, and Create a new object, As always, it is a mess of convenience.
Original English:
Improvements to dynamic data -- several great new features are being added to dynamic data. my favorite new feature is entity templates which enable you to create templates for display, editing, and inserting new instances of an entity (such as a product entity ).