My Family Says I Don't Call Enough

So they read my blog to see what I’m up to, which is strange as I don’t really post about too much personal stuff.  But when I spoke with one of them today, his first question was “so how did the site upgrade go?” 

What got me to thinking about this is I didn’t even realize that most of my blog was down for the better part of 18 hours today before I read Dave’s post about some issues he spotted early this A.M. on 2 sites he knows that recently upgraded to CS2.0.  One of said sites was yours truly.  As much of a vain blogger as I am you’d figure that I would have noticed, and while it’s true that at any given moment I usually have my site open in a Firefox tab, I don’t make a habit of reading individual posts (after all I did write them…maybe late at night when I need to quickly fall asleep I’ll browse over some old posts), which is where the error was occurring (technical details to follow in this post’s sidenote).  The main page and aggregate were unaffected  The point is this:  I do make a habit of checking my logs (IIS/CS exception report/SQL Server/etc) on at least a daily basis, but this exception was obscure enough that I probably would have dismissed it as normal CS exception chatter, and several days could have gone by before I realized anything was awry.

My family reads my blog to see what I’ve been up to.  I read at least half a dozen friends’ (who live within a 5 minute drive from me) blogs on a daily basis to see what they’re up to.  I’ve made friends halfway around the world through this medium.  I’ll admit it, I hate telephones.  If I had it my way everyone would have a blog and that’s how we’d communicate on a regular basis.  That’ll never happen, but I really like “pull” based communication like this.  The phone rings, you have to answer it.  Knock on the door?  Either play Houdini, or be polite and see who it is.  Get an email?  Take your time and respond when you feel like it (within reason of course).  And best of all, keep up with your friends through blogs!

I will say this (and it’s a first for me):  Reading someone else’s weblog today saved my blog’s ass.  God bless the internet.

Sidenote:  Anyone not caring about the technical details of the error I was getting can stop reading now.  The exception my site was so politely showing anyone who happened to be browsing it between the hours of midnight and 3PM today was this one.  I added an RSS image to my category links in the skin-categorylist control via this attribute: ImageUrl="~/Themes/default/images/icon-rss.png", which is strange as tildes should be the safe way to go.  Apparently the .Net runtime didn’t think so and thought it was a directory traversal attempt and said “nope, ain’t havin’ it.”  Wierd.

Filed under:

Comments

# Dave Burke said:

I posted only because I'm a fan, so my intentions were purely selfish.  Was that "email" link there all along?  I'm sorry if it was because I swear I never saw it before.  You could have "saved your blog's ass" quicker. :-)

Friday, February 24, 2006 6:14 AM
# Keyvan Nayyeri said:

First:
Haven't you enabled CoComment for new version? I see that it's available in your page source but doesn't show here :(
Second:
I'm agree with you about phones (:D) I dislike to see that someone wants to talk me when I'm tired or busy. Also some friends try to find how am I via my blog (!) I'm confused. How can they find this?!!!
Third:
That error was one of most strange errors I'd seen before. I sent you an email about it but never could predict that it's related to an image in Category list !

Friday, February 24, 2006 6:38 AM
# Jayson Knight said:

@Keyvan:  Thanks for pointing that out about coco, it took me a few minutes, but I figured it out.  The name of the form for this skin is aspnetForm instead of __aspnetForm, so I guess hardcoding that value isn't a good idea.  Now to figure out how to get the name of the form from code as obviously this isn't a constant value.  As far as why I was getting that error, I have no idea...there isn't much on Google about the "why", just how to fix it.  I'm thinking it has something to do with CS though.  Not a big deal :-).

Friday, February 24, 2006 8:13 AM
# Jayson Knight said:

Well it turns out trying to get the form name from server side code in asp.net 1.1 is next to impossible to do; calling Page.ID/UniqueID/ClientID etc doesn't work (and calling Page.Parent won't even compile under CS).  

The good news is that asp.net 2.0 has a new Form property on the Page object, so calling Page.Form.Name should work.  The even better news is that this is (of course) easy with javascript, just set commentFormName = document.forms[0].name, though this will probably only work for community server as other .Net based blogs might have a subform that contains the comment form.

Saturday, February 25, 2006 1:26 AM
# Keyvan Nayyeri said:

Very well;
Good point. As ASP.NET 2.0 is not based on unique forms, it's easy to work with these properties.
Ignore those images, I think that a few users are interested to use categories RSS and they can find them in each category's page ;)

Saturday, February 25, 2006 6:25 AM
# jayson knight said:

Testing, will be deleted.

Tuesday, March 7, 2006 3:52 AM
# Sara said:

My Friends and family check up on me through my blog too. The phone sucks. I prefer in person, email, chat, or good old-fashioned paper and pen. :)

Tuesday, March 7, 2006 9:53 PM