Hello, I'm attempting to connect to Visual Studio Team Services (formerly Visual Studio Online) with the following command and Alternate Credentials:

Connect-TfsTeamProjectCollection -Collection "https://.visualstudio.com/DefaultCollection" -Credential $myCred

It prompts me for my username and password (the normal windows dialog) which I enter correctly, then it prompts again (this time using single sign-on UI). The goal is to supply a PS-Credential object which should take care of the first windows credential prompt, however I need to not be prompted a second time. Am I doing something wrong here or is this a bug?

Thanks for any inputs
-sean

This command will create a new label
Parameters
Collection
LabelName
Owner
ServerFolder

See command: tf label

As a script developer, I would like to see support for -WhatIf for cmdlets that change state in TFS / VSTS, so that I can better test the scripts before I execute them.

The installer has created a shortcut folder and intuitive , like the image below , I think the shortcut name must be TfsCmdLets

This command will list all shlevesets
Parameters:
Collection
owner
ShelvesetName

see comand: tf shelvesets

This command will show properties of specific file or folder.
Parameters
Collection
Server Path

Server autocomplete should use two data sources:

• Get-TfsRegisteredConfigurationServer
• An MRU list mantained by TfsCmdlets itself, which is updated whenever the user connects to a server

Collection autocomplete should use three data sources:

• Get-TfsRegisteredConfigurationServer
• An MRU list mantained by TfsCmdlets itself, which is updated whenever the user connects to a server
• The list of TPCs in the currently connected Configuration Server (if any)

Project autocomplete should use the following data source:

• The list of projects in the currently connected TPC (if any)

Create a function that returns the version (including Update level) of a TPC/Config Server

Is this module is intended to be executed on a MacOS with the .NET Core and Powershell installed? My computer is a Mac, and when I try it, I can install it with Nuget.exe and start the command let. But I have an error that it doesn't find the System.Windows.Form namespace, which is not available for the MacOS.

Because the CmdLet is a command line and Powershell application, ant that it call Visual Studio, is there a way to remove the System.Windows.Form to compile a MacOS compatible version?

Should provide support to copy/move between folders in the same team project or even between different TPs/TPCs.

Add recursive expansion and the ability to get only users or groups

This command will list all labels on specific server folder
Parameters
Collection
Server Folder

This command will create a new shelveset
Parameters
Collection
ShelvesetName
Comment
Server Folder

See command: tf shelves

I wanted to script some extractions and reports to Excel which combine results from different TFS projects, and these cmdlets work great. However, I am trying to script them unattended, and am having difficulty getting authentication working on the TFS components.

Similar operations to make credentials for SMTP are working fine in my script:

$TFSsecstr = New-Object -TypeName System.Security.SecureString
$TFSPassword.ToCharArray() | ForEach-Object {$TFSsecstr.AppendChar($_)}

# This is what we use for making SMTP
$TFScred = new-object -typename System.Management.Automation.PSCredential -argumentlist $TFSAccount, $TFSsecstr

# I've also tried this one which is internal to the TFS cmdlets
# $TFScred = Get-TfsCredential -UserName $TFSAccount -Password $TFSsecstr

# Passing the credentials here never works, but using the interactive prompt will
Connect-TfsTeamProjectCollection $Collection # -Credential $TFScred

Sign script and installer files using a code signing certificate

Same functionality that this extension

This command will find all workspace with the informed parameters
Parameters:
Collection
Owner
Computer

Add support to Remove-TfsTeamProject, as a replacement to TfsDeleteProject.exe

The four connection cmdlets are inconsistent. Connect-TfsTP and Connect-TfsT must receive the same arguments from Connect-TfsCS and Connect-TfsTPC

When credentials are neither supplied as an argument nor saved in the Windows Credential Manager, no prompt should be shown by PowerShell. Instead, it should default to Integrated Windows Authentication.

Possible solution: http://powershell.org/wp/forums/topic/using-credential-param-as-optional/

When reloading the module, the following exception is thrown:

Add-Type : Cannot add type. The type name 'TfsCmdlets.AssemblyResolver' already exists.
At D:\Projects\Github_Igor\TfsCmdlets\TfsCmdlets\TfsCmdlets\bin\Release\TfsCmdlets\Startup.ps1:9 char:1
+ Add-Type -Language CSharp -TypeDefinition @"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (TfsCmdlets.AssemblyResolver:String) [Add-Type], Exception
    + FullyQualifiedErrorId : TYPE_ALREADY_EXISTS,Microsoft.PowerShell.Commands.AddTypeCommand

Add-Type : Cannot add type. The type name 'PSGenericMethods.MethodInvoker' already exists.
At D:\Projects\Github_Igor\TfsCmdlets\TfsCmdlets\TfsCmdlets\bin\Release\TfsCmdlets\ObjectHelper\ObjectHelper.psm1:503 char:1
+ Add-Type -ErrorAction Stop -TypeDefinition @'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (PSGenericMethods.MethodInvoker:String) [Add-Type], Exception
    + FullyQualifiedErrorId : TYPE_ALREADY_EXISTS,Microsoft.PowerShell.Commands.AddTypeCommand

Module startup logic in Startup.ps1 must check whether the assembly resolver was previously loaded and ignore a reload attempt to prevent the error above.

Should use as a starting point:

• https://github.com/madskristensen/WebCompiler/blob/master/CONTRIBUTING.md
• https://github.com/code-cracker/code-cracker/blob/master/CONTRIBUTING.md

Besides that, should add:

• Coding Style
• Project Structure
• How to build
• Unit tests

Generate automatically TOCs and indexes from cmdlet comment help, in order to support propert navigation in the readthedocs.org website.

Parent-Child relationships would be possible using the Powershell containers, which would allow Move and Create-Item, Get-ChildItem, Get-Parent etc.

Other links probably using the "Add-WorkItemLink" and "Remove-WorkItemLink".

This command will create a mapping folder an existing WorkSpace
Parameters:
ServerFolder
LocalFolder
Collection
WorkSpaceName

This command is based on tf workfold /unmap

This command will remove an existing label
Parameter:
Collection
LabelName

See comand: tf label /delete

Add a new Search-TfsWorkItem that supports the free-text search notation used by in web-based WI search service.

Given the differences in syntax (and the fact that Get-TfsWorkItem already have many different usage scenarios), adding it to a separate cmdlet/function will avoid that Get-TfsWorkItem's syntax gets too convoluted.

This command will show details of specific changeset
Parameters:
Collection
ChangesetNumber
UserName
ServerFolder

See command: tf changeset

As I review the codes, there is no functionality yet to create a new team project.

Arguments:
TfsIteration
TfsTeam

Sometimes it's useful to get "raw" team projects, i.e. those returned by a call to ICss.ListAllProjects(). It's especially useful when there are malformed projects.

In those cases, instead of returning an instance of MS.TFS.WIT.Client.Project, if should return Microsoft.TeamFoundation.Server.ProjectInfo objects.

This command will remove a mapping folder an existing WorkSpace
Parameters:
Folder
Collection
WorkSpaceName

This command is based on tf workfold /unmap

This command will remove an existing item on label
Parameter:
Collection
LabelName
ItemSpec

See comand: tf label /delete

This command will list all files that existing on specific folder
Parameter:
Collection
ServerFolder
WildCard
Status (true - false) - determines if the file is on checkout.

In order to help new developers to detect build-time dependencies (currently it depends on PoShTools and WiX), the PSake build script should be able to detect whether those tools are installed or not, guiding user in case they're missing.

This command will rename an existing workspace.
Parameters:
Collection
NewWorkSpaceName
OldWorkSpaceName
NewOwner

This command will execute an Undo Checkout operation on a file.
Parameters:
Collection
Source File

Using base command: tf undo

This command will remove an existing Shelve.
Parameter:
Collection
ShelvesetName

See command: tf shelves /delete

A cmdlet to return the changed values from a work item.

Idea: when given a work item as an argument, it should return a map (a collection of PSCustomObject? a hashtable?) with the revision number and another map with the changed fields (and their respective values) in that revision.

List the members (groups or users) of a given Team Project

Should prompt for:

• Type (User / Group)
• Filter ("like" on user/group name)
• Scope (Child / Descendant). Descendant should recursively process group membership

Should return:

• User/group name
• List of group a user/group is member of (if -Scope Descendant)

Example use case:

Which team projects is a given user member of?

$user = "John Doe"
Get-TfsTeamProject | ? { Get-TfsTeamProjectMember -Type User -Scope Descendant -Filter $user }

Currently both cmdlets create node recursively when presented with a deep path (e.g. 'Area1/Area2/Area3') where some of the parent nodes (either 'Area1' or 'Area2') don't exist.

That's useful, but may lead to incorrect creation of nodes in case of typos. Having -Force gives the user the opportunity to confirm that's the intended behavior.

Right now, Get-TfsWorkItem does not support saved queries - only ad-hoc ones.

We need a saved query-aware version of Get-TfsWorkItem and CRUD cmdlets to support saved queries

When the Server argument is omitted in a call to Get-TfsTeamProjectCollection the call fails, even if there is a prior call to Connect-TfsConfigurationServer

Haven't seen a real API for this, and I'd be interested in your take 😉

Features

• Should allow copy between different collections/servers;
• Should copy multiple revisions (All, Latest, First, Single, Range)
• Should support WIT change
• Should support field mapping

This command will list a history of a specific folder or file on TFS
Parameters
Collection
Server Path