What's the minimum amount of software I need to install to get the 'tf.exe' program?
相关问题
- Getting error: File extension specified '.webt
- Using TFS command line tf.exe how can I copy a rep
- Is it possible to pass command-line arguments to @
- TFS Power tools Migrate doesn't actually migra
- What is the difference between tfpt scorch and tfp
相关文章
- Linux - change the hostname in the CLI
- Is it possible to do a “destroy history” in TFS?
- How do I make a TeamCity build appear in the TFS B
- TFS vs. JIRA/Bamboo/SVN [closed]
- Why doesn't my .tfignore file ignore my packag
- Node.js multiline input
- Is it possible to create a docker container from T
- How to Move TFS 2010 Build Definition between Proj
In Visual Studio 2017, it can be found here : (Replace {EDITION} by the appropriate edition name ("Enterprise", "Professional", or "Community")
In Visual Studio 2019 Preview, it can be found here :
For reference: these are the required DLLs for Visual Studio 2017 (as did @ijprest for the VS 2010)
They will be in my base VM image. I'm going to use it to pull the latest deployment scripts from VC to a temporary local workspace folder when installing a new server.
(Sorry to post this as an answer, but I don't have enough reputation to comment, which I believe it should have been)
You need to install Team Explorer, it's best to install the version of Team Explorer that matches the version of TFS you are using e.g. if you're using TFS 2010 then install Team Explorer 2010.
2012 version http://www.microsoft.com/en-gb/download/details.aspx?id=30656
2013 version http://www.microsoft.com/en-us/download/details.aspx?id=40776
You also might be interested in the TFS power tools. They add some extra command line features (using
tfpt.exe
) and also add some extra IDE features.You can also try TFS CLI for Node.js which is a cross-platform CLI for Microsoft Team Foundation Server and Visual Studio Team Services.
I'm in a virtual machine, and am trying to keep my VHD as small as possible, so I find Team Explorer is a really heavyweight solution (300+ MB install). As an alternative, I've had some luck copying a minimal set of EXEs/DLLs from a Team Explorer installation to a clean machine (.NET 4.0 is still required, of course).
I've only tried a handful of operations so far, but this set of files (about 8.5 MB) has been enough to get basic source-control functionality via tf.exe:
(It should go without saying that this is a completely unsupported solution, and it doesn't free you from the normal TFS licensing requirements.)
Depending on the operations you perform, you may find that additional DLLs are required. Fortunately, tf.exe will produce a nice error message telling you exactly which ones are missing.
The tf.exe command line is included in the VSTS agent package in folder externals\vstsom.