I'm very unhappy that I have not been able to get back to working on my little pet project lately.  Peter Rysavy was a real pal in going through the program and giving me a hit list of things that can turn it from an experiment into a useful program. And I have a whole class of blogging elementary students and teachers now waiting! I'll get to it, I promise!

It is amazing the amount of coordination that is going to happen to get the various speakers in 32 different cities all on the same page.

If you are anything like me you get a gazillion emails a day and set some aside to read later. Better not do that with the one you got from the DevDays coordinator. There are some serious action items that need to be attended to pretty quickly. Just thought I'd mention it here in case your email is buried already. It was only yesterday afternoon, but it feels like it was days and days ago already!

Update: Even after doing the intelligent updater, my NAV continued to say that I was only running the 1/18 definitions. I finally checked my activity log and saw that indeed, since I ran the Updater, NAV has been catching “W32.Novarg.A@mm“ which is one of the names of this virus.

I could not figure out why my latest virus definitions kept saying 1/18 even after I manually ran live update. Here's why!!

LiveUpdate
LiveUpdate is the easiest way to obtain virus definitions. These virus definitions have undergone full quality assurance testing by Symantec Security Response and are posted to the LiveUpdate servers once each week (usually Wednesdays) unless there is a major virus outbreak. This is the easiest option for most home and small business users, and it provides a very high level of protection along with ease of use.

Intelligent Updater
Intelligent Updater virus definitions have undergone full quality assurance testing by Symantec Security Response. They are posted on U.S. business days (Monday through Friday). They must be downloaded from the Symantec Security Response download virus definitions page and installed manually.

This is just too much, but it made me laugh...

This time it's Eli!

per Kent Sharkey:

Eli Robillard has his triumphant return to MSDN (OK, so he's got two headlines right now) on the ASP.NET Developer Center. This is one on creating a custom framework for handling the assorted errors that may happen on your ASP.NET sites.

When I got asked to present on ASP.NET security at not one but two DevDays events, I accepted [of course] and then afterwards started wondering where I was going to find the time to create a high quality presentation for such a big event. I have a few others that I am currently working on and it is hard (though rewarding and if you are really lucky, educational) work. Since this was my first time at bat for DevDays, I didn't learn for a few more days what is beautiful about this event. You may know by now of course, from reading Brian Goldfarb's weblog that he and Jeff Prosise have created the content for the web security track. Boy oh boy, this is like having my cake and eating it too. So you may be getting locals (and in some cases even local yokels) doing the presentations, but Brian and Jeff will be in many ways right up there on stage with us, feeding our brains...and yours! Of course a lot of the presenters are more than capable of creating their own session materials for this, but the benefit is that there will be very high-quality consistency for every single date.

Considering that she is a pretty attractive woman, I'd be going after the courtroom artist, if I were her!

How often do you have to set up IIS on a remote server and configure it to be accessible from a client box using Visual Studio.NET? Daily? No. Monthly? No. Maybe once every year or two? More like it. I just want to kick myself when I have to go through all of the same problem solving! Oh yeah, forgot to install remote debugging. Oh yeah, forgot to include myself as a VSDebugger group member. The most interesting one this time was getting my webserver to show up in the windows explorer on my client box. I think I am almost back to programming now!

Joel Semeniuk asked me why I haven't written a book and have turned down offers to do so. My joke answer was that I'm too busy with my user group and INETA (he also runs a user group and is on my INETA committee).  I pointed Joel to Chris Anderson's post which perfectly answers this question.

Hey look at that. Guy Barrette who runs the .net user group in Montreal just emailed to let me know that he has become an RD. This is great news. Montreal has been without an RD for a while. Guy and I do a lot of user group stuff together since we are only 2 hours apart so we try to share resources. He also helps out on the user group relations committee  that I chair for INETA. He works with the user groups in Quebec. 

Guy and I got together to bring Steven Smith from ASPAlliance on a little cross-border tour. He will be here in Vermont in a few weeks to play a little and speak at VErmont.NET and then drive up to Montreal to speak at Guy's user group. His Montreal gig is an INETA sponsored event. His trip to Vermont is a “Julie bribed me...“ production.

More on that though later...

I love reading Rick's blog. He's a really smart and innovative guy who has been working with .net for a long time. He is writing applications and also experimenting and his weblog talks about some of the hurdles he runs into while trying to write software and how he gets around them. Very practical, very engaging and educational. Rick lives in Hawaii. I'm always waiting for some surfing pictures! I have fun emailing him once in a while to tell him the temperature - like when it's 20 below (F). It's pretty funny going to a conference and hanging out with Rick from Hawaii and Don Kiely from Alaska.

Farhan - way to GO! Farhan is one of the INETA board members, an author, etc. See more here!

Hip hip hooray. This is my friend who gives me CRAP when I write about him in my blog if for example, he's doing a presentation at a conference.  Hey, somebody's gott brag about you, John.

nah nah nah nah

Big fat congratulations, buddy!

Here is another point that I will be making in my Whidbey BCL talk.

Most people have seen this Base Class Library diagram many times. Here's a picture you have seen a thousand times before where the namespaces are organized hierarchically. There seems to be an attempt to stack them as though they were building blocks, with the fundamentals on the bottom and the UI stuff at the top.

If you look at the WinFX namespace diagram (to which Whidbey is an evolutionary step) you can see that the classes are now grouped not by namespace, but by functionality. I don't recall seeing the classes organized like this before I went to the PDC, though I could be wrong.

Thanks to the Chilean MVP website, I was able to find some jpgs of this poster that I have on my wall. Here is a small one , click on it to get a HUGE one that you can actually read (warning the big one is almost 1MB)

What you will see is, for example, pieces of System.Web in the “presentation” bucket, in the  “Data” bucket in the “Communication” bucket and even in the “Fundamentals” bucket.

Though of course, it will always be important to understand the hierarchy of the classes, this shift in perception will make a developer's evolution to Avalon easier.

Though I wrote about DevDays 2004 eons ago (and that attendees will be getting Whidbey!!), since I am speaking at two events (Hartford 3/2 and Boston 3/16) I just signed up for the devdaysbloggers.net site.  Here is my little “I'll be there” graphic. It doesn't really give me the same jitters as going to PDC, but it's a very important event, because it will reach a lot of developers that would never get to a TechEd or PDC.

I received an “order confirmation from Amazon” email and of course, I hadn't ordered anything. Out of curiousity I looked at the source of the email. It is filled with tags that I don't feel like deciphering or examing, but it looks like it's some secret message or something! If you are curious, I have uploaded a screen shot of the source, rather than paste the text in here and give them some google juice!

This is just a splice. Click on the message to view the whole jpg.

Just because I have had one or ten roadblocks every step of the way of rebuilding my server, I thought that this was very funny (thank goodness my sense of humor has returned after a good nights' sleep!)

When trying to install SQL Server 2000 Ent from my 12/03 MSDN Universal CD on to a Windows 2003 server with all updates applied:

“SQL Server 2000 SP2 is not supported by this version of windows”

hahahahahahahaha

Of course I'm not the first person to see this, but it was a little suprising and the  solution is really just to ignore the message as I see in the many posts that google showed me.

Seems I have gotten side tracked with a lot of hardware issues lately. About two months ago (more?) I decided that I needed more hard drive space on my server. I upgraded to sql server 2000 so that I could accomodate things like Reporting Services and SourceGear Vault (single user). I just couldn't eek along my old 4 gig scsi drive anymore. So a friend sent me a spare 18gb scsi drive, but it was a different type of scsi and I finally received a new scsi adapter card and cable and went to town with my server box on Saturday afternoon. What I really wanted to do was start absolutely from a clean slate and with Windows 2003 server while I was at it. I have to say I went though my own little hell - some incompaitibiliites between the scsi cards, the fact that the floppy disk drive hasn't worked in 3 years (but who cares, right?) and that no matter what I did, the CD refused to be used as a bootable drive and lastly of COURSE, my ethernet card was “incompatible” with win2k3 server (though it turned out that the winxp drivers worked just fine). Because of the scsi problems, I still have some issues to work out with getting my cd player and old drive back into the mix, but I'm not concerned about that - I can just keep moving cables around till it works.

Speaking of cables, there was a little issue of the improperly seated cable which really broke the camel's back!

Anyway, now I am rolling along, have gotten AD setup, IIS installed and have just a few more things to do. One thing I like is that when I set up IIS the first time, I just dumped everyhting into the default web server - now I have set up a separate web server just for my stuff. So what I have left is pull my web sites back intot he new IIS, install SQL 2K and bring the databases back in, install Reporting Services and install SourceGear.

Then it's back to the regular work.

Why do I say Win2K3 instead of Win2003? It saves me ONE keystroke!

Not to say that they are the only ones, but these two really stood out for me. Was it just because one was about a great outdoor gear chain and the other had something to do with Vermont? No, they both go much deeper than that.

The first gives some true visions from a successful retailer on future technology and how it will help his business - and this is something we developers should be paying attention to! It's almost like a hot stock tip! And notice how Robert slips in that the guy uses a tablet?

The other is Robert's take on why he is suddenly very disappointed with the whole phenom of the dean blogging thing. I have watched Halley Suitt and Robert get very caught up in the campaign (and Dave Winer was here helping them out just last week) and I wasn't sure if it was because it involved blogging or because they are really behind what Dean wants to do for the U.S. I sure hope that he (Dean) is kidding when he says he wants the whole country to be just like Vermont - land of the $7.50/hour service jobs (and many people who need to have more than one job), taxes that are out of synch with incomes and let's just say a little problem when it comes to health insurance. Robert accepts that the Dean Blog isn't blogging as he knows and loves it, but politics as usual. There's more than politics to Robert's post and I dug the whole thing.

Rich was kind enough to try to help me after all of the illogical trouble I was having wtih my server installation. He took a close look in the box and said the scsi cable wasn't plugged in properly. “Oh No!” I sasid, I have reseated that a # of times, it's a software problem. I was at a point where if I booted up to the win2000 disk, I could see, format, partition, read, etc. the NEW disk, but when I tried to continute the win2k3 server setup onto that new disk, I kept getting the blue screen of death. He finally convinced me to let him at it and - gulp - he was right. The install is now almost done. Damn! There's a developer joke in there somewhere about it really being a hardware problem after all, but the real issue was that I was so focused on the software side of things, I didn't take the hardware end seriously enough. Embarrassing? Not really, it could have been a thousand things - incompatible hardware etc, and I *had* considered and reseated those cables. Educational - yup!

The Rocket Scientist/Carpenter reference is because Rich's college degree is in physics, but he now happily works for himself as a carpenter.