Skip to main content

Posts

Sliding and Absolute expiration in Caching

Caching Mechanism and Its Expirations ASP.net cache or AppFabric Caching are ways to  increase the performance of the web application by r educing server round trips to database. However the validity of the cached data needs to be ensured, to enforce this, we have the following options 1. Dependency Mechanisms:      Files, SQL Cache Dependency etc This ensures that the cache is re-validated or refreshed once a dependent has changed or been altered 2.  Expire Cache:      The cache will expire after a time frame and the newer items will be added to cache when ever accessed or processed after expiry.  In Cache Expiry, we have the following options 1. Absolute Expiration:   Absolute expiration means It will expire cache after some time period set at the time of activating cache. This will be absolute expiration whether cache will be used or not It will expire the cache. This type of expiration used to  cache data which are not frequently changing. 2. Sliding Expiration: 

Constructors for user defined Exceptions in C#

The following are the rules that are to be adhered to when creating any custom user  defined exception. 1. Follow the Naming convention so that the self-explanatory name of the exception ends with Exception like: ArgumentNullException. 2. The following constructors should be defined public NewException() public NewException(string message) public NewException(string message, Exception exception) protected or private NewException(SerializationInfo serializationInfo, StreamingContext streamingContext) These ensure that the created Exception satisfies the default rules of User Defined Exceptions. [Also Satisfies FxCop Validation] -- Saravanan