Getting something better than “Server not found.” from WCF in Silverlight redux

I have had a lot of question lately about my blog post concerning “Server not found.” messages coming from WCF to Silverlight. I decided to create a quick post that provides a sample application that has everything wired up with some test buttons.

The application just has some buttons at the bottom of the screen that make calls to the service operations. Here is what the code looks like for the WCF service:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Runtime.Serialization;

using System.ServiceModel;

using System.Text;

using System.ServiceModel.Activation;

using Web.Core;

namespace ServerExceptions.Web

{

    // NOTE: You can use the "Rename" command on the "Refactor" menu to change the class name "BusinessService" in code, svc and config file together.

    [WcfErrorBehavior()]

    [WcfSilverlightFaultBehavior()]

    public class BusinessService : IBusinessService

    {

        public void RaiseException()

        {

            throw new Exception("Can't log in to the database.");

        }

        public string RaiseInvalidOperation()

        {

            throw new InvalidOperationException("You can't call this method!");

        }

        public void RaiseIndexOutOfRange()

        {

            throw new IndexOutOfRangeException();

        }

        public string GetCustomerName()

        {

            return "Matt Duffield";

        }

    };

}

This is a contrived example but the most important thing to note are the attributes above the service definition.

WcfErrorBehavior

WcfSilverlightFaultBehavior

It is these attributes that give us the ability to capture the error and send it back down the wire to the client. If you comment out the attributes and try any example that throws an error you will get our favorite message:

Read more: Matt Duffield

Posted via email from Jasper-net