Client Timeout accessing asmx web service

I had a console utility generating a bunch of content files, that are accessing an asmx web service method to do the job. The utility ran fine for many days in production, but it started timing out yesterday.

The exception message read ‘Operation has timed out’. After checking on the IIS I upped the Timeout in the Properties dialog to 900 seconds. That didn’t help either.

Finally figured out that the webservice proxy class on the client also has a Timeout property that needs to be updated. As I updated it to 10 minutes, the utility was able to generate the content files without timing out.

MyWebSvcProxyClass myProxy = new MyWebSvcProxyClass();
// it's a client side timeout set to 10 minutes
myProxy. Timeout = 600000;

More on this: http://www.dotnetbips.com/articles/1d925079-5e0f-4098-a30f-a7dbbb311330.aspx

Breaking changes in Visual Studio SDK 1.1

There might be more, but these were the ones that came to light immediately.

• ProjectBase.Files along with the parent “Project” folder does not belong to the Visual Studio SDK 1.1. It is now available as a separate download from Codeplex as MPF. You will need to update the base paths in your custom project files to point to the new location (wherever you place the MPF files) - The whole Project folder is no more part of the SDK, it has been moved to codeplex as a community project MPF

Visual Studio Managed Package Framework for Projects (MPFProj)
http://www.codeplex.com/mpfproj/SourceControl/ListDownloadableCommits.aspx
The ProjectBase.Files is the key file that needs to be added as an import to your VSX package project file
<Import Project=”$(ProjectBasePath)\ProjectBase.Files” />
ProjectBasePath is the location of the MPF Source

• As a result of the above change, classes like ProjectFactory, ProjectNode, VsMenus are now in a different namespace called Microsoft.VisualStudio.Project.ProjectFactory (Old namespace was Microsoft.VisualStudio.Package)

Providing InnerXml to XElement

In my latest project, I dived in to the world of Linq, by using Linq to Sql. As I have loads of XML related application logic I also got to use Linq to XML. We have XElement class given to us from System.Xml.Linq namespace which has loads of usefulness over the old world XmlElement class. So there I go admiring XElement, but wait I don’t have an InnerXml method, that lot of us have gotten used since the MSXML DOM days.

I came up with providing an Extension method InnerXml() on XElement.

public static string InnerXml(this XElement element)
{
    StringBuilder innerXml = new StringBuilder();

    foreach (XNode node in element.Nodes())
    {
        // append node's xml string to innerXml
        innerXml.Append(node.ToString());
    }
    return innerXml.ToString();
}

Someone was exactly looking for this on StackOverflow (the awesome tech QnA site that is in private beta right now)