I have live-blogged three MIX10 Windows Phone sessions. You can access them below:
First session - introduction to WP7S
Despite this post's title looking a bit like a spam subject line, this is a serious post about an issue we ran into today at work. We have a stored procedure that gathers some statistics for us, and a really strange thing was happening with it. When run from SSMS, it took less than one second to execute, but when run from code, it actually timed out while executing over two minutes. Why would it run so fast through SSMS and yet so slow through our code?
If you haven't heard about the Windows 7 activation hack yet, you will soon. Journalists are already busy blowing it out of proportion, saying things like "in no time, you will be able to buy a copy of Windows 7 in China or Vietnam for less than a dollar" (CNET) and "despite all the posturing and puff, at no point during the Vista lifecycle so far have pirates NOT been able to successfully bypass Windows Genuine Advantage" (ZDNet).
I was looking through some files in the leaked Windows Mobile 6.5 ROMs floating around the wonderful XDA-Developers site when I stumbled upon what looks like an Outlook Mobile help file. That file mentions Exchange 2010 and some fascinating new features. The two features that are of particular interest are SMS syncing and sending SMS messages from inside Outlook and OWA.
I realize I'm posting this on April 1st, but rest assured, this is not a joke posting, despite the odd title. I just came across a Channel 9 video that discusses a new feature in VB10, implicit line continuation. It's basically a way to avoid having to put an underscore at the end of a line in order to tell the VB compiler that the statement isn't finished yet. While I think that it's an incredibly cool feature, I also think that it should not be implemented.
