Monday, January 29, 2007

Windows Vista has been released for public consumption! That makes it sound like Vista is some sort of sandwich or something...

I thought that the official release date was going to be tomorrow (1/30), but you can download the Ultimate Extras now. So far, the BitLocker stuff and the Hold 'Em game are out there. In other news, you can get the 1.5 version of Windows OneCare, which supports Vista. It's not even beta!

Now all I need is the full release of PowerShell for Vista and I'll be set (check, PowerShell for Vista has been released)!

(and the update for Visual Studio 2005 to run on Vista)

(and updated drivers/software for my HP printer)

(and updated drivers/software for my Logitech MX1000 mouse (check!))

(and updated drivers/software for my Logitech 880 remote)

(and a pony)

posted on Monday, January 29, 2007 6:36:40 PM (Central Standard Time, UTC-06:00)  #    Comments [0]
 Thursday, January 18, 2007

I probably should have just submitted this one to Overheard at the Office, but I'd rather post it here.

"It's not that I'm lazy, it's just that I want to be thorough."

This was from one of my coworkers who was speaking to a user upstairs.

I found it hilarious.

posted on Thursday, January 18, 2007 1:20:52 PM (Central Standard Time, UTC-06:00)  #    Comments [0]
 Tuesday, January 16, 2007

I recently moved my RSS reading habits over to Google Reader, primarily because I read feeds at work and home both and I'd rather not have to keep my feeds synchronized in both places. The new design is a million times better than the old design, too.

Anyway, a feature that Google Reader provides is a location to view "Shared" items. I've started sharing items that I find interesting from my daily feed reading. So far, it is mainly some cool Engadget posts and some deals, but if anyone is interested, you can view my Google Reader Shared items here.

So now, you can see my blogroll (at the right side of the screen), my bookmarks (thank you del.icio.us!), and feed items I find interesting.

Just wait untill I post a public calendar! Hah!

posted on Tuesday, January 16, 2007 1:03:08 PM (Central Standard Time, UTC-06:00)  #    Comments [0]

We're in the process of migrating to .NET 2.0 at work and one of the the things we've encountered is a problem with remoting between .NET 1.1 and 2.0 frameworks.

This is our scenario in a nutshell.

An application is upgraded to 2.0 but is still referencing a 1.1 component. This works fine until the 1.1 component remotes to a 1.1 server. The client is running under the 2.0 framework while the server is running under the 1.1 framework. We can't upgrade the server because there are still other 1.1 clients out there as well.

What's funny about this is that it will work sometimes. Interoperability between 1.1 and 2.0 is actually fairly solid... unless you're serializing a DateTime across the wire. If you're sending a DateTime between the two frameworks, you'll see this error:

Exception: System.ArgumentOutOfRangeException
Message: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks.
Parameter name: ticks

If you were to change the server side over to run under .NET 2.0, you won't see the problem anymore. On the plus side, Microsoft has released a hotfix to address this issue (and even more information here) that specifically patches the 1.1 framework. The problem is that you've got to contact Microsoft to get the hotfix.

I'm hoping that by posting this, I will let others know about it and maybe even to get Microsoft to release it for download.

Then again, maybe no one else has to deal with this issue :-)

posted on Tuesday, January 16, 2007 12:38:32 PM (Central Standard Time, UTC-06:00)  #    Comments [0]
 Wednesday, January 10, 2007

A recent post by Lee Holmes on breaking your writer's (blogger's?) block is prompting this post. I recently finished reading Steve McConnell's book, Code Complete*, over the Christmas holidays and the book was amazing. As I read it, I began taking lists of things I wanted to post on that were excellent advice... and ran into a block because there was just so much I wanted to say about. I still plan on writing more detailed posts on the issue but, as Lee suggests, I need to just get out here and post more.

So anyway.

Recently, I posted an entry on calculating file hashes with PowerShell and promptly had to put an update because the PowerShell Community Extensions (PsCx) had provided a better file hash function. The good thing about PsCx is that it really provides a good example of PowerShell code and has a lot of cmdlets that drive home automating PowerShell for your needs.

One of my favorite functions is incredibly simple but it highlights how you can save just a few keystrokes for more productivity. The Edit-File function uses a predefined variable that points to an EXE path and runs the EXE with the specified parameter. There is also an alias for it (e) so you can type something like "e somefile.txt" and it will open. I like this method a little better than actually renaming notepad.exe to n.exe (*cough* Scott Hanselman *cough* :-) ). It actually prompted me to create multiple, similar functions so that I can open files in different editors (I use Ultra-Edit, Notepad2, Notepad++, or who knows what else) without having to respecify the editor variable. Now I type "u somefile.txt" to open a file in Ultra-Edit.

This also prompted me to set up the winmerge function below:

function winmerge ([string]$path1, [string]$path2) {

    $winmergePath = "c:\program files\winmerge\winmerge.exe"
    . $winmergePath $path1 $path2
}

It allows me to quickly see the comparisons between two different files without having to preselect them with the mouse. It is simple, but quite convenient. And I also don't have to go adding all sorts of random directories to my PATH just so I can get to them more quickly.

So there you go: my PowerShell automation.

I also promised some unrelated updates. On Monday, January 8, I had LASIK surgery on both of my eyes to correct my extreme nearsightedness. The whole operation took 15 minutes and the only discomfort I had was a headache and some stinging eyes on the day of the operation. Since that time, my left eye can already see with 20/15 vision. My right eye is still a little fuzzy, but that is supposed to clear up in another day or so - it took the laser twice as long to correct my right eye as it did my left eye!

If anyone is interested in more details on my experiences with LASIK, I'd be happy to provide a follow-up post on it.

* - Jeff Atwood really should get some sort of referral rewards for recommending Code Complete... I mean seriously...

posted on Wednesday, January 10, 2007 9:38:44 PM (Central Standard Time, UTC-06:00)  #    Comments [0]