.NET news » Search results
Search results for query "pages" (52):
SharePoint's Delegate Control Power
One complaint about Microsoft Windows SharePoint Services (WSS) 2.0 and Microsoft SharePoint Portal Server 2003 was the difficulty in making changes to the environment after it was deployed. Officially, changing a site definition isn't supported after it has been used to create other sites.
Now, Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server (MOSS) 2007 offer many ways to make changes to sites after they have been provisioned. The introduction of SharePoint Features has opened up an entire world to changing master pages, page layouts, and pages themselves. Further, SharePoint now includes a new technique—delegate controls—that allows for more fine-grained control over parts of the page.
Online Article: Top-Ten Annotations and Remarks about the Wonderful and Powerful New Set of Features in ASP.NET 2.0
You'll still write a good deal of code in ASP.NET 2.0.Don't completely trust those who say that ASP.NET 2.0 cuts 70% of the amount of code you're called to write. You'll end up writing more or less the same quantity of code, but you'll write code of different quality. You'll have more components and less boilerplate code to tie together pages and controls. Features like the provider model, data source controls, and master pages make coding easier and equally effective. But since there's no magic behind, you have to learn the implications of each feature you employ. In the end, ASP.NET 2.0 comes with code behind, not magic behind.
ASP.NET AJAX: Providing Visual Feedback with the UpdateProgress Control
Microsoft's ASP.NET AJAX Framework helps page developers design more interactive web pages by streamlining the postback mechanism. In traditional web pages, a full postback involves the browser re-requesting the page, which is then re-rendered. This re-rendered page markup is returned, in its entirety, to the browser for display. Ajax techniques improve the user's experience in two primary ways through the use of partial postbacks: first, a partial postback is asynchronous, meaning that the user can still interact with the page while waiting for the partial postback to complete; second, and more importantly, because a partial page postback updates only a particular region (or regions) of a page, less data needs to be shuttled between the client and the server, resulting in a quicker and smoother experience..


Syndicate