Click here to Skip to main content
Click here to Skip to main content
 
Add your own
alternative version

Frictionless WCF service consumption in Silverlight - Part 3: Benefits of transparent asynchrony with respect to unit testing

, 26 May 2011 MIT
Simplifying unit testing of View Models which use asynchronous WCF service calls.
FrictSLUnitTest.zip
Source
Sample.Silverlight.WCF
Infrastructure
Actions
Services
Properties
Shared
Utility
Views
Sample.Silverlight.WCF.Tests
Properties
Sample.Silverlight.WCF.Tests.Clumsy
Properties
DataSources
Sample.Silverlight.WCF.Web.Services.Task.datasource
Service References
ServiceReference1
configuration.svcinfo
configuration91.svcinfo
Reference.svcmap
TaskService.disco
TaskService.wsdl
ServiceReferences.ClientConfig
Sample.Silverlight.WCF.Tests.Clumsy.Web
Properties
Sample.Silverlight.WCF.Web
Properties
Services
TaskService.svc
Tools
NUnit
nunit.framework.dll
nunit.silverlight.dll
Rhino.Mocks
Castle.Core-Silverlight.dll
Castle.DynamicProxy-Silverlight.dll
Rhino.Mocks 3.5.Silverlight.dll
using System;
using System.Windows;
using Microsoft.Silverlight.Testing;

namespace Sample.Silverlight.WCF.Tests.Clumsy
{
	public partial class App : Application
	{

		public App()
		{
			this.Startup += this.Application_Startup;
			this.Exit += this.Application_Exit;
			this.UnhandledException += this.Application_UnhandledException;

			InitializeComponent();
		}

		private void Application_Startup(object sender, StartupEventArgs e)
		{
			RootVisual = UnitTestSystem.CreateTestPage();
		}

		private void Application_Exit(object sender, EventArgs e)
		{

		}
		private void Application_UnhandledException(object sender, ApplicationUnhandledExceptionEventArgs e)
		{
			// If the app is running outside of the debugger then report the exception using
			// the browser's exception mechanism. On IE this will display it a yellow alert 
			// icon in the status bar and Firefox will display a script error.
			if (!System.Diagnostics.Debugger.IsAttached)
			{

				// NOTE: This will allow the application to continue running after an exception has been thrown
				// but not handled. 
				// For production applications this error handling should be replaced with something that will 
				// report the error to the website and stop the application.
				e.Handled = true;
				Deployment.Current.Dispatcher.BeginInvoke(delegate { ReportErrorToDOM(e); });
			}
		}
		private void ReportErrorToDOM(ApplicationUnhandledExceptionEventArgs e)
		{
			try
			{
				string errorMsg = e.ExceptionObject.Message + e.ExceptionObject.StackTrace;
				errorMsg = errorMsg.Replace('"', '\'').Replace("\r\n", @"\n");

				System.Windows.Browser.HtmlPage.Window.Eval("throw new Error(\"Unhandled Error in Silverlight Application " + errorMsg + "\");");
			}
			catch (Exception)
			{
			}
		}
	}
}

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The MIT License

Share

About the Author

Yevhen Bobrov
Software Developer http://blog.xtalion.com
Ukraine Ukraine
No Biography provided
Follow on   Twitter

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.141223.1 | Last Updated 26 May 2011
Article Copyright 2011 by Yevhen Bobrov
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid