| 10 Tips for Great .NET Programming |
| .NET Magazine |
| I’ve compiled a list of 10 tips to make your .NET development more effective and productive. To help as many developers as possible, the tips span the technology’s whole spectrum—from ADO.NET to ASP.NET, from the CLR to the Framework, and from Windows Forms to Web Services. Here they are, counting up to the ones I anticipate will have the most impact. |
|
| An Easy-To-Use CacheManager |
| The Code Project |
| Using Cache is easy. Basically, you only need to use Insert to store data and use Get to access data. But you have to decide if the data is already in the cache, which in turn requires that you have a scheme to build a key. So you still have to do some work. The CacheManager serves to shield you from the details of managing the cache key. |
|
| Application Cache Viewer |
| ASP Alliance |
| ASP.NET and the .NET Framework automagically cache pages as they are accessed by site visitors. This obviously speeds up the response time of your website. In addition to ASP.NET's ability to cache pages for us, we are able to store selectively cache items for use in our applications. This article demonstrates a very simple cache viewer that will display items stored in the local applications cache. |
|
| Application of the Cache Subsystem for Web Applications |
| C#Today |
| In this article, Eric Rhea explores two approaches to utilizing the caching system. First, he talks about how to make use of the cache subsystem from the web-form code. Then, he takes a look at exploring how to make use of the cache subsystem in the code behind. While doing this, he seeks three answers: (1) how to improve performance, (2) how to make use of similar techniques in both code areas, and (3) how to cache an object which is indeterminate in length and whose values you do not know in advance, and one which you cannot cache using the web-form directive. |
|
| Build an XML Serialized Object |
| Visual Studio Magazine |
| Almost every Web application needs to store global configuration settings. Traditional Active Server Pages (ASP) Web applications often stored this data in a database. However, database storage has drawbacks: It's terribly inefficient to query the database each time you need to retrieve a setting, and some data, such as your database connection string, isn't appropriate for storage in a database. Many developers try to get around these two caveats by storing settings in Application variables initialized in the global.asa file. The problem with this approach is that changing the value of one of these Application variables in the global.asa file forces the entire ASP application to reload, leading to periods of downtime. |
|
| Cache and Carry With ASP.NET |
| Visual Basic Programmers Journal |
| ASP.NET applies broad caching support at various levels - from precompiled pages, to persisted page output, to an application-accessible Cache object that joins and improves your old ASP acquaintances Session and Application. In this column, I'll introduce you to ASP.NET's caching options and show you how to work with each option. |
|
| Caching Multiple Versions of a Page |
| ASP Alliance |
| Often, an application may have a Web page that can receive different requests for different information that will be rendered on the same page; hence, the presentation of the information will mostly be changed for each request. |
|
| Cutting Edge: Implement Custom Cache Dependencies in ASP.NET 1.x |
| MSDN |
| Get ASP.NET 2.0 functionality now. |
|
| Data Caching in ASP.NET |
| C# Corner |
| ASP.NET has built-in CACHE ENGINE that is used by ASP.NET pages to store and retrieve objects across HTTP requests. The ASP.NET cache is private to each application and stores objects in memory. The lifetime of the cache is equivalent to the lifetime of the application; that is, when the application is restarted, the cache is recreated. |
|
| Page Output Caching, Part 1 |
| MSDN |
| About a year ago, I wrote a column that provided an overview of the Caching functionality found in ASP.NET. In this month's column, we'll explode that topic and focus on one aspect of ASP.NET Caching—page output caching. |
|
| XML Web Service Caching Strategies |
| MSDN |
| Despite advancements in network and processor speeds, performance remains a key concern among application developers. So whether you are writing an XML Web service, pushing image bitmaps to a video card, or even engineering that next great processing chip, you will invariably want to consider utilizing a universal mechanism for improving performance: a cache. |
|
