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

Url: http://silverlight.net

Url: http://sdn.nl

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.

Url: https://mvp.support.microsoft.com/profile/Shawn...

In building my Silverlight RC example using ADO.NET Data Services for Entity Framework and NHibernate I ran into what I think is a common pattern.  I am writing an editor for XBox game data. The model for this data uses decorator tables in the database which are modeled as a common "Product" class and derived "Game", "Console" and "Accessory" classes.  In the application I am using paging to only look at fifty results at once. This works fine on both sides. 

Url: http://www.geekdinners.com/DinnerInstance.aspx?...

After digging and some prodding by a PM at Microsoft, I realize that the relative URI story in WebClient is different that I expected.  I am not sure whether this changed from previous versions but Beta 2 and the RC this is the way that Relative URI's work in WebClient:

Url: http://silverlight-tour.com

Url: http://www.saffroninteractive.com/silverlight.html

When making web requests in Silverlight 2, its easy to start with the simple WebClient class. In fact, it supports making simple requests (DownloadStringAsync and OpenReadAsync) as well as uploading through the class. On the other hand there are some that swear by the WebRequest route. What's the big difference?

Url: http://weblogs.asp.net/scottgu/archive/2008/09/...

Url: http://www.silverlightdata.com

Url: http://silverlight-tour.com

Url: http://citybistrohoboken.com

Url: http://wildermuth.com/DirtyLittleSecrets

Url: http://wildermuth.com/DirtyLittleSecrets

I was crufting up a sample LINQ to JSON example today to post in my blog but something odd happened.  I couldn't find a public service that both used JSON and supports a security policy file.  Let me clarify that.

There was a great turnout for tonight Atlanta Geek Dinner. I had a lot of fun and really enjoyed the conversations that were to be had (technical, political and even some SharePoint).

Url: http://weblogs.asp.net/jgalloway/archive/2008/0...