Setting Up a Workspace Using Team Explorer Everywhere on Linux

Setting up a workspace using Team Explorer Everywhere on Linux

You'll need to create working folder mappings between your local folder and the server items you wish to correspond to.

For example:

tf workfold -map -login:secretUsername,secretPassword -server:http://secretHost:8080 -workspace:KOLOBI '$/TeamProject/Project' '/home/me/project'

Then from the /home/me/project directory (or whatever you pick), you can just execute tf get .

TFVC WSL can't create new local workspace

TFVC WSL can't create new local workspace

There is an issue about the TEE version before 14.135 on that agent:

Linux+TFVC checkout failures after Azure DevOps 2020 RC1 upgrade

To resolve that issue, we need update the TEE to 14.135 and copy two files ( slf4j-api-1.7.19.jar and slf4j-log4j12-1.7.19.jar) into the lib directory of new TEE from the lib directory of previous Tee (14.134).

Create a new high level folder in TFS without downloading all project using Team Explorer Everywhere command line Linux

Git-TF does not require a folder to have been created in TFS already.

git tf configure http://tfs:8080/tfs/DefaultCollection $/Path/To/{folder}

git tf checkin --deep

And the new project folder is created

Convert TFS workspace from local to server in Eclipse

When you create or edit a workspace, you can specify whether its location is Local or Server. To edit the workspace follow below steps:

1. In Project Explorer or Package Explorer, right-click an
   Eclipse project that is under version control, point to Team,
   and click Manage Workspaces.

2. The Workspaces dialog box appears. It shows you the list of your Team Foundation Server workspaces.
3. Then select the one you want to convert, click Edit; the Edit Workspace dialog box appears just as
   below screenshot:

Note: Local workspaces are only supported for Team Foundation Server 2012 and above.

How to check out (get) a specific version/revision of source using Team Explorer Everywhere CLC

The tf get command takes a "-version:" option where the changeset number can be specified:

$ tf get -version:12345

For more information, see:

$ tf help get

The help text does not specify the format of the "-version:" value, but plain numbers work for me in order to specify changesets.

How do I stop Team Explorer Everywhere from seeing a deleted folder as a detected change

When you delete an item that Team Foundation Version Control expects to exist on-disk, it detects that deletion and displays that as a "detected change". Note that this is merely an informational message. It is not a "pending change" and it cannot be undone, nor can it be checked in to the server, at least not without promoting the detected change to a pending change via a call to tf delete.

However, if you're worried about accidentally promoting that change, or if you're just tired of seeing it, you can instruct the client that you shouldn't have those in the first place. The easiest way to do this is to do a get on that path of a previous version that didn't have these files, namely changeset 1:

tf get /version:C1 $/PROJECT

Now your local working folders are in sync with your workspace mappings and there should be no more detected changes to $/PROJECT.

We aren't getting any feedback from the TF CLC command in Linux when trying to access our TFS 2010 server

Logs are not in ~/Microsoft, they're in ~/.microsoft. (Note the dot.)

It's difficult to say what the problem is without the logs: you're not specifying a command in the first examples, as -login is not a command, it's an option. You need to specify the login credentials option along with a command. For example:

tf workspaces -login:... -collection:...

But without the logs, it's difficult to tell what the problem is.

---

Related Topics