Blogs

The basic scenario is as follows:  I have done quite a bit of WPF programming in the past (since back when it was WinFx).  I feel pretty damn good about the bindings in WPF, and I feel like I have wrapped my head around binding and dependency properties pretty well.  So, I thought when I decided to write Silverlight 2 apps rather than straight to the vein, white horse, WPF apps, it would be a very similar feeling.  The feeling was abruptly interrupted by the evilness of the ElementName Binding param.  For those of you who have spent time writing WPF apps, you will know the joy of binding element properties to each other and having no problems.  It's easy to take such things for granted.

This morning I found myself wrestling with SSIS to convert a string from a flat file to a unique identifier via a Data Flow inside of an SSIS package.  I figured this would be a rather trivial case (the midget was kicking my ass!).  I use guids all over for application development and for database keys.  They are very useful, and very dependable.  Here is a line from my flat file:

61898d4c-3a1b-4736-9a36-eb90a23322e0|:|10/13/2008 11:59:58 PM|:|74afebfe-9523-4977-b5f6-5154b6c91211

Anyone see anything wrong with this?  I didn't see anything wrong, outside of the silly |:| delimiter (I don't want to get started on that <rant/> <--- rant with no content!). 

I've been very excited recently by the release of Windows Azure, and rest of the Microsoft suite of cloud based services.  I downloaded all of the sdk's, signed up for all the invitation tokens I could, and began writing code.  The Visual Studio templates for Windows Azure projects makes getting your first Azure project up and running super simple.  I did run into one issues with the project templates setting up my first project.