The problem with Silverlight applications is that you cannot perform time consuming operations in the UI thread. If you were able to force and wait for the service to respond this would hand the Silverlight and its environment (the browser) while the operation is completed. This is why the only allowed way to consume services in a Silverlight application is asynchronously.
Of course this is something unusual at first, but in the long run it is actually helpful to decouple the view and service layer.
I hope this is helpful.
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>