~mkw

I have been a self employed developer for a little over 2 years and in that time have taught myself a number of rules. My Component rule is pretty common and goes as follows.

This shining city on a hill will never forget you.

So here I am, 3:27 am coding away when my incessant ctrl+c & ctrl+v cause the vacuum enclosed finely coiled tungsten in my head to get red hot; my mouth drops open as I realize how wicked cool generics are and how they will save me far more time than I had been thinking!

Early today ASP.NET GUru Scott Guthrie responded to a news story about his disapperance, letting this writer know that he has very busy the last few months. We are all happy to hear he is OK and look forward to his syndicated return to the blogosphere...the original news story can be found below.

disAssociated Press - Friday May 21, 2004

With over 150 days since he has entered anything into his blog, industry watchers and tech luminaries have resigned to face the fact that Scott Guthrie has disappeared permanently.

In my current application, the vast majority of the web site is broken into content ‘parts’ that can all be edited through a built in content manager. Pages consist of one or multiple parts which are elements of HTML persisted to the SQL database. In order to improve performance I wanted to look at some techniques for caching these content elements and coupled with my desire to learn new things I decided to use the Cache class directly instead of the more common methods of Output Caching.

I wanted to toss this out there in case there is some new or as of yet unpacthed vulnerability. This morning I had an unusual string of errors whereas someone began trying to supplant the VIEWSTATE into the URL and in turn causing an error.

Gavin is giving away a free copy of his nTierGen product to weblogs.asp.net bloggers, either he is being really nice or figured that it would be good marketing and really raise his rank on google if we all blogged to thank him!