Migrating Applications from WSE 2.0 to 3.0

  • Article

The Web Services Enhancements for Microsoft .NET (WSE) attempts to maintain a degree of backward compatibility between versions. However, changes to WSE that help improve security, correctness, or functionality require rewriting portions of code when upgrading to the latest version of WSE.

Note

WSE 2.0-enabled applications do not interoperate with WSE 3.0-enabled applications, because WSE 3.0 supports newer versions of some of the WS-* specifications. The Windows Communication Foundation (WCF) supports the same version of the WS-* specifications as WSE 3.0. WSE 2.0 and WSE 3.0 client applications can run side-by-side with the .NET Framework 2.0. WSE 2.0 and WSE 3.0-enabled Web services can be hosted on the same computer, but they must be in separate virtual directories. For more information on the version of the WS-* specifications that WSE 3.0 supports, see Web Service Specifications Supported by WSE.

The following steps provide an overview of how to convert WSE 2.0 applications to WSE 3.0. For more details, click the links for the specific migration topics.

  1. Convert Visual Studio .NET 2003 projects to Visual Studio 2005 projects using the Visual Studio Conversion Wizard.
    The file format for Visual Studio solution and projects files has changed for Visual Studio 2005, so existing Visual Studio .NET 2003 projects must be converted prior to use in Visual Studio 2005. Also, Web-based projects, such as ASP.NET Web service projects, are now called Web sites in Visual Studio 2005.
    To convert Visual Studio .NET 2003 projects, open them in Visual Studio 2005. When opened in Visual Studio 2005, the Visual Studio Conversion Wizard starts to direct you through the conversion process.

  2. Convert configuration files using the WSE Settings 3.0 Tool.
    For more details, see How to: Migrate Configuration Files from WSE 2.0 to 3.0.

  3. Update any lines of code that use the WSE 2.0 namespaces to use the WSE 3.0 namespaces.

    1. From the Edit menu, point to Find and Replace, and then select Quick Replace.
      The Find and Replace dialog appears.

    2. Replace all instances of Microsoft.Web.Services2 with Microsoft.Web.Services3 in the project.

      Note

      All classes in the Microsoft.Web.Services2.Policy namespace have been replaced by other classes and they now reside in the Microsoft.Web.Services3.Design namespace.

  4. Optionally, convert code that secures SOAP messages to use custom policy assertions.
    For more details, see How to: Migrate Code that Secures a SOAP Message without Policy to Use Custom Policy Assertions.

  5. Convert WSE 2.0 policy files to the WSE 3.0 policy file format.
    For more details, see How to: Migrate Policy Files from WSE 2.0 to 3.0.

  6. Convert code that uses X509SecurityToken security tokens to retrieve the X.509 certificates using the X.509 certificate classes in the .NET Framework 2.0.
    For more details, see How to: Migrate Code that Uses X509SecurityToken Security Tokens from WSE 2.0 to 3.0.

  7. Convert code that sends attachments using DIME to use MTOM.
    For more details, see How to: Migrate Code that Uses DIME Attachments to Use MTOM.

  8. Convert custom filters to custom policy assertions.
    For more details, see How to: Migrate Custom Filters to Custom Policy Assertions.

In This Section