.NET news » Search results

Search results for query "default.asp" (4):

Custom Paging in ASP.NET 2.0 with SQL Server 2005

A common pattern in web development is providing paged access to data. Rather than displaying the entire contents of a report or database table to an end user, developers often show only a subset of records per web page, with controls for moving from page to page. With ASP.NET 1.x, the DataGrid made paging incredibly simple - just set the AllowPaging property to True and add a few lines of code in the PageIndexChanged event handler and you were done! ASP.NET 2.0's GridView makes the process even simpler - just check the Enable Paging option from the GridView's smart tag - no code needed.

Of course nothing is free in life, and the tradeoff you make with the ease of checking a checkbox to enable paging (or, in the DataGrid's case, writing a couple lines of code) is performance. Out of the box, the DataGrid and GridView use default paging, which is a simple paging model that returns all of the records for each every page of data shown. When paging through small amounts of data (dozens to a hundred or so records), this inefficiency is likely outweighed by the ease of adding the feature. However, if you want to page through thousands, tens of thousands, or hundreds of thousands of records the default paging model is not viable.

The alternative to default paging is custom paging, in which you are tasked with writing code that intelligently grabs the correct subset of data. It requires a bit more work, but is essential when dealing with sufficiently-sized data...

2006-03-14 18:00:00   Source: Custom Paging in ASP.NET 2.0 with SQL Server 2005   Tags: ASP.NET Database

Cache Integration: Building and Using Custom OutputCache Providers in ASP.NET

With the .NET Framework 4.0, you can now boost performance by replacing the default ASP.NET output cache with your own implementation. We show you how to do this with the MongoDB "NoSQL" database in a simple ASP.NET MVC app and then we swap out the custom provider to leverage features of Windows Azure AppFabric.

Output Caching in ASP.NET 2.0

One of the most sure-fire ways to improve a web application's performance is to employ caching. Caching takes some expensive operation and stores its results in a quickly accessible location. ASP.NET version 1.0 introduced two flavors of caching:

  • Output Caching - caches the entire rendered markup of an ASP.NET web page or User Control for a specified duration.
  • Data Caching - a programmatically-accessible, in-memory data cache for storing objects in the web server's memory.

For a more in-depth discussion on ASP.NET 1.x's caching capabilities, refer to Scott McFarland's Caching with ASP.NET and Steve Smith's ASP.NET Caching: Techniques and Best Practices articles.

In ASP.NET 2.0, the caching system has been extended to include SQL cache dependencies, cache profiles, and post-cache substitution for output cached pages. The Caching for Performance section of the ASP.NET 2.0 QuickStarts provides a good overview of ASP.NET 2.0's caching options. This article explores output caching in ASP.NET 2.0, starting with an overview of output caching and followed by a detailed look at creating pages that include both cached and non-cached markup using fragment caching and post-cache substitution techniques.

2006-12-12 18:00:00   Source: Output Caching in ASP.NET 2.0   Tags: ASP.NET Performance

Extending Asp.Net role based Security with Custom Security Module (Permission Based, Page Level Authorization)

This project intends to extend the default Asp.Net role based Security to include Permission Based / Page Level Authorization Layer. Works with both ASP.Net and Asp.Net MVC. Permission rules to Allow/Deny access to website resources (like "Folder/File.aspx" or "Controller/Action" ) are stored in DB
2011-11-12 04:28:00   Source: Extending Asp.Net role based Security with Custom...   Tags: Internet