Confusions on new controls under ASP. NET 2.0

We all know that in ASP. under net2.0, Microsoft provides a new system control, some of which are quite useful. For example, the membership member management system and step-by-step wizard control have saved us a lot of time, in addition, for example, the upgraded gridview from the DataGrid sometimes doesn't feel so good.

This control provides us with great convenience while also losing flexibility. For example, you can directly specify an SQL statement to complete data access, and display it on pages, sorting is easier than eating. As we all know, this is contrary to our hierarchical logical architecture design, which creates an embarrassing situation. It is difficult for new users to make powerful and complete functions only by relying on these controls.ProgramEven worse, it encapsulates a lot of operations, and we don't know how it operates in the background. For new users, in case of a problem, they don't know where the problem is, and experienced programmers certainly won't adopt such ugly design. When you use it to complete the upgrade and other operations, it is inconvenient to verify the input content, and the control will generate a large viewstate field during running, resulting in reduced efficiency, as for the paging performance of large data volumes, let alone, although dataset can be serialized in binary format, the results are still unsatisfactory. So where is the value of such a control?

Although the gridview can be used for paging, it also provides paging styles. It is very troublesome to manually define them. In other words, if you need very powerful data operations, such as multi-column sorting, summarization, export, aggregation, and even drag-and-drop, and other complex functions, it is better to use other means to achieve this, for example, commercial controls and smart client platforms are more convenient. The Design of dozens of style attributes in the gridview is also very bad, although you can use these attributes to make a very fancy user interface, however, once a project has dozens of gridview entries, the modification work is simply unimaginable. Therefore, we have to use a powerful tool like CSS to define its style.

The SQL data source control is also quite simple. Although there is no practical value in large projects, I think there are still some benefits, at least it can improve the confidence of people who are not very interested in programming. I thought that I used DW's automatic coding function as a personal website.CodeIt is so ugly, and the logic is so chaotic. Later, I invested in programming with full enthusiasm. Otherwise, I will not go to this day.

I'm optimistic about the data source control called objectdatasource. Why? It can control the program logic freely in the background, making every step of the Operation transparent, with the powerful features provided by generics, our program looks good. The data source saves a lot of time for our front-end data binding. Taking advantage of this feature can bring a lot of convenience to our programs.

Anyone familiar with Microsoft starterkit knows that there is a sample program for a personal website, which is a typical example of an object data source application. In this program, ASP is used. the new control features provided by net2.0 have been fully realized, and a lot of logic work has been completed with a small amount of code. However, it is only a personal website, and the work in many places is not enough. For example, I can submit an empty form without any check.

In short, the rational use of these new controls will greatly improve efficiency, and also give friends with a low level of programming a C # sharp new experience. In terms of functionality, I personally think it is much better than DW's three-legged cat trick. Many people are still discussing how to program in DW. Actually, DW is more suitable for interface creation.

I am currently working on ASP. the paging controls under net 2.0 are upgraded from msdn sqlpager in 1.1. One is the migration of programs to 2.0, and the other is the form of user controls, in this way, the paging style can be freely expanded based on your preferences. You can use the data access block of Microsoft's latest enterprise database to communicate with the database. You can use the data cache or read only the required records, improved efficiency. It has been basically completed and will be released on the new day. Thank you for your attention. At the same time, due to its own level and limited energy, it is inevitable to have some shortcomings and shortcomings, but you can rest assured that this control is developedSource code, You can freely expand it. If there is a problem, you can also troubleshoot and correct it from the source code.

On the big data paging issue, it seems interesting to see a foreigner on the internet today. Recently, I will take some time to translate and give it to you. Here is the source address, the general idea is to use SQL Server 2005

Row_number ()
Feature to work.