Open
Description
Beginning in Jan 2020 and with TFS 2020 on-prem, the SOAP interface will no longer be supported.
https://docs.microsoft.com/en-us/azure/devops/integrate/concepts/wit-client-om-deprecation?view=azure-devops
Right now we support the reading capabilities through the REST interfaces, but do not generate patches to send back to the server. We also have quite a few SOAP-isms in the code to make the REST and SOAP clients behave in similar ways so we really just can swap one implementation for another.
It's a year out, but I'd like to get the discussion going about what we would like to do about this change. Some ideas:
- Drop support in the next major for SOAP (e.g. delete) and go REST all the way. We would need to give people a heads up by marking the SOAP classes as deprecated.
- Stop support for SOAP in the major, but kep the code. Code marked as deprecated with instructions to move to REST, but we won't do any enhancements to the SOAP implementations and minimal bug fixes. This allows people to use the latest version against older TFS instances.
- Some version of the first two where we phase it out over time. We don't have any telemetry so we can't measure the impact. All we have is the scream test (either by the community saying something or NuGet downloads dropping)
@MattKotsenas @pelavall Other ideas?
Metadata
Assignees
Labels
No labels