Silverlight 4 Upgrade Breaks Silverlight Debugging Experience

A design change in the Silverlight 4 installer now causes older developer runtime to be upgraded when a newer client runtime installer is executed.  This causes the Silverlight debugging components to be uninstalled, and breaks the debugging experience: The workaround for this is to install the latest Silverlight developer runtime, which you can find at…


Making the Silverlight-Enabled WCF Service in Dev10 Beta 1 Work with Silverlight 2

In Dev10 Beta 1, the Silverlight-enabled WCF Service template is the version used for Silverlight 3 beta.  This uses a custom binding to enable binary encoding, and is incompatible with Silverlight 2 applications.  If you attempt to add a reference to it, you’ll see errors like the following: (note that you might also see this…

1

Switching Your Visual Studio Environment Between Silverlight 2 and Silverlight 3

With the release of Silverlight 3 Beta, you’ll may want to try out the new features.  Unfortunately, Silverlight 3 Beta is a developer only release (no end-user runtime, no GoLive license), so you might end up going back and forth.  Even more unfortunate is that Visual Studio 2008 doesn’t have much room to create a…

1

Silverlight 3 Tools Issue: New WCF Template is Broken by Silverlight 2 SDK

In Silverlight 3, we’ve introduced support for binary message encoding for WCF services, which should give a performance boost.  Silverlight 2, as you may recall, only supports basicHttpBinding.  The new binding is the default for Silverlight-enabled WCF services created with the Silverlight 3 Tools. If you’ve upgraded from the Silverlight 2 Tools for Visual Studio…

13