importing WSE2 to version 3

Hot Topic

Anybody can tell me what is wrong????
Help with a Xbox Lan please
AzMan: Has anyone created an HTML/Web management console as an alternative to the AzMan MMC?
Expose a VB.net function to unmanaged c++
Referencing
Datamining SQl queries from excel documents
How can i check if my username and password are correct with FtpWebResponse
Using SqlCeCommand SetRange with Wildcards
Need help getting the information of the task manager (Ctrl+Alt+Del)
Calling a stored SQL Proceedure from VB

.NET Development

VS Express - Common Modules
Add a reference at runtime
Access to a smartcard private key
Parsing data from MSQL to TextBox
Cannot unload assemblies that you create and load by using script in XSLT
ADO.NET 2.0 Batch support
what are the practical Limitations of Dataset and datatable
ArgumentOutOfRangeException with Dir serv
Making a Client Wait for Server Response
Rename Root Node in XML

importing WSE2 to version 3

Hello!
I'm having a problem importing my old WSE version 2.0 to version 3.0. In the logs asks me to make the configuration manualy. But I don't quite succeded in doing this. I can't make it create trace log files and the application doesn't work any more after conversion.

Answer this question

importing WSE2 to version 3

  • mrwise

    The easiest way is to make a new policy, if the old one couldn't be imported succesfully.

  • MartinMSJ

    It's no use editing the config file, because they a regenerated again everytime I run the application.

  • mig16

    I don't have any reference to microsoft.web.services2 in my application, only to microsoft.web.services3! I can't do any changes to the server side. The server is a java web service and is for public use I am only developing a client which shoud connect to it. What namespace should I change   I think that it is already changed because I have something like:

    public partial class JustizERVServiceWse:Microsoft.Web.Services3.WebServicesClientProtocol

    in the Reference.cs file.

  • lenora

    the error log is the following:
    WARNING: Policy Section was not imported as WSE 3.0 Policy has changed significantly. Please use the Policy Wizard to create a new Policy.

    Well I've recreated the policy manualy, but I still can't authenticate to the web service.

    Another strange thing is that I still have configurations for WSE 2.0 (well I have it installed on my system for Visual Studio 2003, but I don't use it in my 2005 project):

    <section name="microsoft.web.services2" type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration, Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

    Why is that

  • Robert Magowan

    Can you send some more info There are changes in WSE3 that brakes compatibility to WSE2 code, but only on some cases.

  • KombatNT

    I was talking about the configuration file.

  • Alan Reed

    Ok. Change the section handler for the correct section handler for WSE 3. You can do this by changing the microsoft.web.services2 into 3, and changing the namespace and assembly version name. You must also change the section name in the configuration file.

    Then point to the policy file that you have created with the wizard. By adding this configuration

     <microsoft.web.services3>
      <policy fileName="wse3policyCache.config"/>
     </microsoft.web.services3>

    Perform this in both client and server side.

  • importing WSE2 to version 3
Answer this question