This has probably been covered in some tutorial videos or "silverlight 3 what's new"s, but due to the fact that I spent the better half of an hour googling about ways to do it, I guess also posting it here for reference won't hurt. Problem: when calling a WCF service from Silverlight 2, if the service throws an exception, in Silverlight you get a CommunicationException with some mumbo-jumbo in it, not the actual exception or Fault declared on the service. Fix: in Silverlight 3 there is built-in support...

If you have a Silverlight 3 Beta 1 DataGrid that, for some reason, is not refreshing when its bound ItemsSource changes, like so... <data:DataGrid ItemsSource="{Binding Path=Parameters}" AutoGenerateColumns="false" IsReadOnly="True" > ...you might want to know that it's a bug in the beta. I actually spent about 2 days on and off on this issue, researching a workaround and googling for it with no results. Only today, more on a guess than anything else, I did this: <data:DataGrid ItemsSource="{Binding...

Small gotcha today after installing the Silverlight 3 beta "suite" - runtime, visual studio 2008 tools and blend 3 preview. (side note: if you install the Silverlight 3 runtime BEFORE the visual studio 2008 tools, then the tools installation fails because it tries to reinstall the runtime... so either uninstall the runtime or don't install it at all standalone, the tools installation will take care of it) Opening an existing Silverlight 2 project triggered the conversion to SL3, which worked fine....