Url: http://www.microsoft.com/azure/data.mspx
Url: http://www.jeff.wilcox.name/2008/11/04/test-fra...
Url: http://www.developerfusion.com/code/4678/perman...
Url: http://notatpdc.com/presentations/
Url: http://www.sellsbrothers.com/news/showTopic.asp...
Url: http://www.atldotnet.org/default.aspx
Url: http://www.dnrtv.com/default.aspx?showNum=127
Url: http://www.engadget.com/2008/10/26/netflix-fina...
Url: http://www.geekdinners.com/DinnerInstance.aspx?...
Here is a quick but fun tip for working with Silverlight 2. I found that many people are using Isolated Storage for saving user preferences or other small pieces of information. When I look at the code, I am surprised by how much trouble they are going through to save small bits of data. That's where Isolated Storage Settings come in.
Url: http://silverlight-tour.com
Not a biggie, but just so that anyone that reads my blog knows...its "Silverlight 2", not "Silverlight 2.0". Wasn't my decision, but its the fact. Journalists and bloggers alike have been throwing out "2.0" a lot lately and after being hammered by some well-meaning Microsofties about the name, I just wanted to make sure everyone knows the right way.
In meeting with a client (Schoolmaster.nl who is building a cool LOB app), we came across the problem of one of their components was throwing Image Failed Javascript errors. Handling them in the App.UnhandledException event didn't help because the errors were surfaced outside the plug-in, directly to Javascript. Immediately I use the VisualTreeHelper to walk the entire XAML tree (including nested templates) to just add an event handler on to every ImageFailed events to try and suppress these errors.
I've started updating my sites that use Silverlight 2 to the RTW bits. So far I've got silverlight-tour.com and wildermuth.com updated. SilverlightData.com will have to wait a few days as I have a completely new example that is more complete and dynamically switches between NHibernate and Entity Framework. Look for an announcement on that this weekend.
There is a known problem with ADO.NET Data Services today that is important if you (or your server) lives in specific timezones. The problem is associated with the way that the Silverlight Data Services Library constructs their URI for searches.
Url: http://wildermuth.com/dirtylittlesecrets
Its been quite quiet on my site these last week or so. I am traveling doing a couple of European conferences so my blogging is light. I do expect to deliver my new edition of my ScreenCast (Shawn Wildermuth's Dirty Little Secrets) this friday and I'll have a completely wrap up of the conferences once they are complete. Stay tuned for a lot more content in the next week or so.