Azure-devops-docs: Documentation is totally out of sync and complexity of the libraries make it almost impossible to use

Created on 16 Feb 2019  Â·  3Comments  Â·  Source: MicrosoftDocs/azure-devops-docs

Hi,
I've been working with creating tools for TFS since 2008 version and it feels like the libraries are growing like a Hydra, chop of one head and two new will be created. At the same time the documentation is decreasing so you have to make a lot of assumptions and wild guesses most of the time. That has led me to try the hardest to skip using the libraries and simply use my own http/https wrappers directly against the REST API, I only use the libraries where it's in any other way impossible to accomplish what I need (mostly working with the security model, altering groups, users, rights etc). Isn't the libraries ment to be a support to the users? Imagine buying a new car and not get any service or even a manual to read for it, comparison is valid because if you have any questions there's noone answering, only the same mantra: "I will add this and that person to the question", but after that, only a big silence!


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

devopprod doc-bug

Most helpful comment

@wnjenkin - one "easy" fix is adding links to the .NET reference (https://docs.microsoft.com/dotnet/api/index?view=azure-devops-dotnet) and .NET samples (https://github.com/microsoft/vsts-dotnet-samples).

This page should be reorganized as the landing page for .NET developers (wanting to integrate with Azure DevOps). Currently the page is focused on the client packages, which are obviously important but not the "lead story". A better starting point would be a good reference example that then links into the packages, other samples, and reference.

All 3 comments

@wnjenkin - one "easy" fix is adding links to the .NET reference (https://docs.microsoft.com/dotnet/api/index?view=azure-devops-dotnet) and .NET samples (https://github.com/microsoft/vsts-dotnet-samples).

This page should be reorganized as the landing page for .NET developers (wanting to integrate with Azure DevOps). Currently the page is focused on the client packages, which are obviously important but not the "lead story". A better starting point would be a good reference example that then links into the packages, other samples, and reference.

Hi @LennartAJansson, I've created a user story on my backlog to capture this work and will be in touch. Thanks so much for the feedback.

Hi @LennartAJansson, This content update is slated for "future," so I wanted to let you know that I'll be closing this issue, however, once the updated content is published, you'll be notified via this thread. Thanks for helping us to help others better.

Was this page helpful?
0 / 5 - 0 ratings