The new Enter-TfsShell
and Exit-TfsShell
cmdlets streamline the invocation of the "Azure DevOps Shell" mode. When invoked, shows a banner with the module version and activates the custom console prompt. The custom prompt displays the currently connected Azure DevOps org/server.
Invoke-TfsRestApi
can be used to streamline calls to the Azure DevOps REST API for scenarios/APIs not yet covered by TfsCmdlets.
Lastly, Get-TfsVersion
returns version information on a given team project collection / organization. Currently, only Azure DevOps Services organizations are supported. Support for TFS and Azure DevOps Server will be added in a future release.
In the process, they've been generalized and converted to aliases to their new "generic" counterparts (*-TfsWorkItemQueryItem
), much like the Area/Iteration cmdlets.
Now both TfsCmdlets.Types.ps1xml and TfsCmdlets.Format.ps1xml files are generated during build time from YAML files with ps1xmlgen. That offers a much better experience to edit/mantain PowerShell's type/format XML files.
This improvement is way overdue, but now we have the first set of argument completers. Any cmdlets with the arguments -Server
, -Collection
and -Project
can be "Tab-completed".
Now, to connect to a Azure DevOps (or TFS) collection/organization/project/team you can use optionally use one of the aliases below:
- Connect-TfsConfigurationServer
- ctfssvr
- Connect-TfsTeamProjectCollection
- Connect-AzdoOrganization
- Connect-TfsOrganization
- ctfs
- Connect-TfsTeamProject
- ctfstp
- Connect-TfsTeam
- ctfsteam
- Fix iteration processing in Set-TfsTeam (72f0fc0), (e15d1ee)
- Fix build when in Release configuration (6a795ce)
- Fix classification node (area/iteration) retrieval for old APIs (0df3616)
- Fix TFS Client Library version retrieval (a9ac849)
- Fix Azure DevOps Shell command prompt
- Fix Disconnect-* issues
- Incremental build is currently disabled in the default Visual Studio Code Build task, as it's a bit inconsistent.