Often in ASP.NET application we see a code which looks like this one: if ( Cache [ "SomeData" ] != null ) { string name = ( ( SomeClass ) Cache [ "SomeData" ] ) . Name ; //..... } Experienced developer, even if he is not a paranoiac, will find possible problem immediately — NullReferenceException . That’s because
Similar Posts
My friend Steve Smith who wrote this article has solved a major problem for me. With his permission I'm duplicating some of his code here. About one in
A few days ago I posted a question I had gotten on email (look here for complete post) We use Page.Cache to store temporary data, but we have recently
There is some magic to the way SQL Server 2005 cache dependencies work with the OutputCache directive, and I finally had the chance to dig a little deeper
Here's a quick tip for something pretty neat in ASP.NET 2.0. You can specifyoutput cache profiles in the application configuration like so (this is under
