none
Support multiple Web Service versions with one implementation RRS feed

  • Question

  • Hi,

    I have the following requirement, currently we target one web service version for example: https://webservices.sandbox.netsuite.com/wsdl/v2017_1_0/netsuite.wsdl, everything works fine except when there is a new version that we need to start testing while keeping the old in production for example: https://webservices.sandbox.netsuite.com/wsdl/v2017_2_0/netsuite.wsdl

    my requirement is as follow: I would like to have each version of the wsdl reference in separate project and be able to use the same service client code to target a desired version using a config file.

    Any help would be appreciated.

    Regards,

    Fahd


    Thursday, October 5, 2017 12:58 PM

All replies

  • Hi Fahd,

    >> I would like to have each version of the wsdl reference in separate project and be able to use the same service client code to target a desired version using a config file.

    What will you change for current Service Contract implementation?

    Will you change anything in Service Interface?

    I suggest you check WCF Service Versioning.

    # Service Versioning

    https://docs.microsoft.com/en-us/dotnet/framework/wcf/service-versioning#service-orientation-and-versioning

    # Versioning Strategies

    https://msdn.microsoft.com/en-us/library/ff384251.aspx

    Best Regards,

    Edward


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, October 6, 2017 5:07 AM
  • No change to the interface that's goal so that whenever there is a new version, I will create a new project load and run it against a the same implementation to see if there is any changes then run regression unit tests.

    I am using the service locator for other implementations but I am not sure how to apply it to different web service versions potentially living on separate assemblies.

    And for the web service, it is provided by third party so I have no control besides WCF will add configuration bottlenecks that I would like to avoid. if you need to see code snippets, please do let me know.

    Regards,

    Fahd

    Friday, October 6, 2017 12:47 PM
  • my requirement is as follow: I would like to have each version of the wsdl reference in separate project and be able to use the same service client code to target a desired version using a config file.

    Maybe a Service Layer client-side classlib project would work. One client-side code able to access multiple services with all client-side configs in one config file.

    Friday, October 6, 2017 10:05 PM