RE: WSE 2 and 3 dual mode, problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Tim,
\par
\par From your description, you have two winform clients, one use WSE2 and another use WSE3. And the server-side WSE2 and WSE3 service are hosted in the same ASP.NET application/project, and you got problem with them to work together, right?
\par
\par If this is the case, I think the problem should be due to some collision between the two WSE framework. As we know, WSE just use a soapextension(injected in ASP.NET webservice processing pipeline) to do those WSE processing. If you use both ones in your project, that means there contains two extensions there, there is no gurantee that this will work. Is it possible that the two WSE parts be separated in two application. One ASP.NET 1.1 webservice and another ASP.NET 2.0 webservice?
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par \pard\li720 --------------------
\par From: "Tim Mackey" <tim.mackey@xxxxxxxxxxxxxxxx>
\par Subject: WSE 2 and 3 dual mode, problems
\par Date: Wed, 21 Nov 2007 16:29:58 -0000
\par
\par hi,
\par i am in the situation of needing to support a WSE2 winforms client and a
\par WSE3 winforms client.
\par i have set up the web site with a separate ASMX file for each, and both
\par clients work if they are the first to access their respective web service.
\par the WSE2 client works consistently, but the WSE3 client fails after an
\par undetermined time, it seems to be related to any activity on the WSE2
\par service. possibly the WSE2 soapExtensionImporterType is overriding the WSE3
\par one somehow. i tried clearing this section in the WSE3 section of
\par web.config, but that had no effect. 'touching' the web.config file allows
\par both clients to begin working again. is there a better approach to this
\par problem than what i am currently doing?
\par
\par relevant sections from web.config below.
\par thanks in advance for any help
\par tim
\par
\par <?xml version="1.0"?>
\par <configuration>
\par <configSections>
\par <section name="microsoft.web.services3"
\par type="Microsoft.Web.Services3.Configuration.WebServicesConfiguration,
\par Microsoft.Web.Services3,Version=3.0.0.0,Culture=neutral,
\par PublicKeyToken=31bf3856ad364e35" />
\par <section name="microsoft.web.services2"
\par type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
\par Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
\par PublicKeyToken=31bf3856ad364e35" />
\par </configSections>
\par
\par ...
\par
\par <compilation defaultLanguage="c#" debug="true">
\par <assemblies>
\par <add assembly="Microsoft.Web.Services2, Version=2.0.0.0,
\par Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
\par <add assembly="Microsoft.Web.Services3, Version=3.0.0.0,
\par Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
\par
\par ...
\par
\par <location path="WSE2.asmx">
\par <system.web>
\par <webServices>
\par <soapExtensionTypes>
\par <add type="Microsoft.Web.Services2.WebServicesExtension,
\par Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
\par PublicKeyToken=31bf3856ad364e35" priority="1" group="0" />
\par </soapExtensionTypes>
\par </webServices>
\par </system.web>
\par </location>
\par
\par <location path="WSE3.asmx">
\par <system.web>
\par <webServices>
\par <soapServerProtocolFactory
\par type="Microsoft.Web.Services3.WseProtocolFactory, Microsoft.Web.Services3,
\par Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
\par <soapExtensionImporterTypes>
\par <add
\par type="Microsoft.Web.Services3.Description.WseExtensionImporter,
\par Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral,
\par PublicKeyToken=31bf3856ad364e35"/>
\par </soapExtensionImporterTypes>
\par </webServices>
\par </system.web>
\par </location>
\par
\par ...
\par
\par <microsoft.web.services3>
\par <policy fileName="policyCache3.config"/>
\par <security>
\par <securityTokenManager>
\par <add type="CustomUsernameTokenManager3"
\par namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
\par localName="UsernameToken"/>
\par </securityTokenManager>
\par </security>
\par </microsoft.web.services3>
\par
\par <microsoft.web.services2>
\par <messaging>
\par <maxRequestLength>10000</maxRequestLength>
\par </messaging>
\par <security>
\par <securityTokenManager type="CustomUsernameTokenManager2"
\par xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
\par qname="wsse:UsernameToken" />
\par <defaultTtlInSeconds>86400</defaultTtlInSeconds>
\par <timeToleranceInSeconds>86400</timeToleranceInSeconds>
\par </security>
\par <policy>
\par <cache name="policyCache2.config" />
\par </policy>
\par </microsoft.web.services2>
\par
\par \pard
\par
\par }