As everyone probably guessed, my last post was generated directly on my iPAQ talking over my wireless network at home...

Some interesting observations...

• You get very wierd behavior if you take an assembly that was compiled against the desktop framework and run it on the device. Visual Studio will silently let you do this, compile, and try to run - however you will get odd errors. I saw "You need a new version of the framework", "Unexpected error", and "TypeLoadException". In the end I had to copy all my shared code from BlogX (the service proxies and runtime helper classes) into new CF projects.
  
• Guid.NewGuid doesn't exist, but it took 1 google search to find the right hack for this. I'll have to follow up with the device folks to see if this is fixed in Whidbey.
  
• XmlSerialization isn't in the .NET CF... I'm suprised they didn't just write a reflection based version, but I bet it would have been way too slow. This made me comment out a bunch of stuff from my shared BlogX libraries.
  
• TabOrder isn't supported (or maybe my machine is broken). I couldn't get the TabOrder UI in VS to show up, so tabbing around between the fields on the device isn't in the right order (I can fix this in code though). Of course, many devices don't have keyboards so this probably isn't that big of a deal.

Overall, I'm pretty amazed that it only took 1 hour to get a smart client blog posting app written, of course I'll credit this to the great modularity of BlogX (ha ha!!!).