Search

Source: Channel 9

He covers several topics including these:

• Setting up your service
• Debugging issues with "add service reference"
• Handling Faults: How to get exceptions propogated from the sderver to Silverlight
• How to use Fiddler to use with WCF
• Using the new relative address feature in Silverlight 4

Source: Shawn Wildermuth's Blog

So today I put together this little video to show off a couple of concepts:

• Debugging while Tombstoning
• Handling State during Tombstoning
• Getting Comfortable with
• Debugging Callbacks during Tasks

Source: Shawn Wildermuth's blog

When you are running your application and you want to test it tombstoning (e.g. deactivating), you should notice that Visual Studio stops debugging when that happens. When you return to your applciation (via the back button or in the case of a chooser, once you've choosen something), you'll get a black screen. This isn't a bug...its a feature!

Suppose you use Firefox as your default web browser and you are a Silverlight developer using Visual Studio.  You may have been frustrated at times in being able to get the debugger to attach to your breakpoints.  You’ve triple-checked that you are in debug mode, that the Silverlight checkbox is marked in the hosting web application’s property pages and it still is not breaking for you.  You stare at the dreaded empty red circle in Visual Studio reading the tooltip of “No debug symbols have been loaded…” a thousand times.

I am really happy with the experience. Debugging with the emulator is fast too, but there are times when you want to make sure it works on the device and that the performance is what you expect on the device.

In the previous part from the series, Shawn talked about the phone itself.

Recently, we came across a bug with the Silverlight Business Application with respect to an Out of Browser application. In the RTM bits for Silverlight 4 Tools a new feature was added to enable a better debugging experience with Out of Browser application. The feature basically launched the app in OOB window when run with the debugger attached. If you have tried that with the business application template, you will notice that the app does not run. It crashes with an exception, that the URI path is not valid.

Today Mozilla released FireFox 3.6.4, and in the new version plugins are isolated in their own process.  As such,  the VS debugger attaches to “firefox.exe” instead of the new process FireFox creates named “plugin-container.exe” when you start debugging a silverlight application.  There are 2 fairly easy fixes.

This question on Stack Overflow referring to an error when using the new WPF behavior TranslateZoomRotate.

First of all, its nice to see the new behavior included with Expression Blend 4 in use.  

The TranslateZoomRotate behavior provides support for gesture-based rotating, scaling and position translation just by dropping the behavior onto an element.

On this blog we normally talk about building and accessing WCF services, since that is the recommended way to build services for Silverlight. However, we continue to support ASMX services using the familiar “Add Service Reference” feature.