The majority of the time it works well with WCF services with some tweaks, as this MSDN article explains.

But what about old .ASMX .NET webservices?

There’s a couple things to understand before we handle those soap faults.

First, by limitations on the browser stack that I won’t go into detail, Silverlight can’t handle HTTP 500 responses. So our first task is to make sure that any ASMX responses are HTTP 200.

Second, ASMX faults are not as nice as WCF faults. So we have to handle them a little bit differently once we get them in Silverlight.

Let’s get started on the first task.

The easiest way of making sure all .ASMX responses are sent out of your server as HTTP 200 is to create a IHttpHandler.

To create your IHttpHandler, simply create a standard .NET Class Library, reference System.Web and add a regular class with this code in it:

After creating your IHttpHandler, register it on your .ASMX website web.config

This will basically make every single request to asmx webservices return HTTP 200, no matter what.

By now, if you run your Silverlight client you’ll probably stop getting the super annoying "The remote server returned an error: NotFound." response.

Good. Now all we have to do is get the proper fault details on your asynchronous Silverlight request. Simple:

If you want things really tidy (I didn’t had time for this, sorry), try to write your own error descriptor and use FaultException<T>.

Happy Silverlight coding!

Good reading:

Creating and Handling Faults in Silverlight
https://msdn.microsoft.com/en-us/library/dd470096(VS.96).aspx

Data Performance and Fault Strategies in Silverlight 3
https://msdn.microsoft.com/en-us/magazine/ee294456.aspx

Rafael Rivera did a great job explaining what it is.

Alongside the new features of Terminal Services (that I’m not sure if are public yet so I’ll not mention), I reckon this will give the space that the Windows team needs to make future versions of Windows rock even more.

You can read Rafael’s post here.

Windows 7 is looking absolutely fantastic by the way :)

This KB article tells you why this happens :)

https://support.microsoft.com/kb/961661

This might help you :)

// Add all namespaces on your document 

public static class MyExtensions
{
    public static XmlNamespaceManager CreateNamespaceManager(this XDocument doc)
    {
        XmlNamespaceManager nsmgr = new XmlNamespaceManager(doc.CreateReader().NameTable);
        
        foreach (XAttribute attr in doc.Root.Attributes())
        {
            if (attr.IsNamespaceDeclaration)
                nsmgr.AddNamespace(attr.Name.LocalName, attr.Value);
        }

        return nsmgr;
    }
} 

Then query your XDocument using the System.Xml.XPath extensions:

XDocForm.XPathSelectElement("/my:Field1/my:Field2/my:Level1", XmlForm.CreateNamespaceManager());

Rule "Previous releases of Microsoft Visual Studio 2008" failed.
A previous release of Microsoft Visual Studio 2008 is installed on this computer. Upgrade Microsoft Visual Studio 2008 to the SP1 before installing SQL Server 2008.

This error is documented on KB 956139, "Actions that are required before you install SQL Server 2008 on a computer that has Visual Studio 2008 or the prerelease version of SQL Server 2008 installed".

I had Visual Studio SP1 (version 9.0.30729.1 SP) properly installed on my machine, so why this message? Well, with a quick monitoring using Process Monitor I noticed that the setup process was looking for ServicePack information on the WoW64 registry key, that was outdated:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DevDiv\VS\Servicing\9.0\IDE\1033

In order to fix it, you can update the SP and SPIndex entries to 1 and the SPName to SP1; just like the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VS\Servicing\9.0\BSLN\1033:"