This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Update AzureUri for onprem support and handle VssResourceNotFound error#123
Merged
Update AzureUri for onprem support and handle VssResourceNotFound error#123
Conversation
dhoehna
approved these changes
Feb 20, 2024
| <comment>Shown in Widget when first pinned while waiting for data to load.</comment> | ||
| </data> | ||
| <data name="ErrorMessage.InitializeVssConnectionFailure" xml:space="preserve"> | ||
| <value>Failed creating the Vss Connection</value> |
Contributor
There was a problem hiding this comment.
Please add comments for all these strings.
EricJohnson327
approved these changes
Feb 22, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the pull request
Updates AzureUri to handle the format for On-Premeses DevOps servers (aka "onprem").
Also adds a specific error handling message for VssResourceNotFound error, which is what happens if you call an API that the devops server does not support. This was found against a DevOps Express install, which does not appear to have full rest API functionality.
References and relevant issues
Closes #45
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist