Adding support for ClientOM 19 and 20 in PowerShell task SDK #1140
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.
This pull request updates the credential handling logic in the
ServerOMFunctions.ps1PowerShell script to improve compatibility with newer versions of the Client Object Model (ClientOM) for Azure DevOps/TFS. The changes prioritize the use of newer authentication types when available, while maintaining support for legacy credentials.Credential Handling Improvements:
Get-TfsClientCredentialsfunction now attempts to useVssClientCredentials(available in ClientOM 14+) before falling back to the legacyTfsClientCredentials. It also dynamically selects the appropriate federated credential type (VssOAuthAccessTokenCredentialfor ClientOM 16+, orVssOAuthCredentialfor ClientOM 14).Assembly Resolution Enhancements:
Get-OMTypefunction now additionally checks forInteractive.dllwhen resolving types, ensuring support for scenarios whereVssClientCredentialshas moved to this assembly in ClientOM 16+.