Destroy: A new feature for Orcas

Version Control Server blog: Orcas destroy feature, merging with labels

Buck Hodges — Sat, 31 Mar 2007 04:09:08 GMT

The Version Control Server blog has shown some signs of life. Bill Tutt has written a couple of posts.

Version Control Server blog: Orcas destroy feature, merging with labels

RSS It All — Sat, 31 Mar 2007 04:25:38 GMT

The Version Control Server blog has shown some signs of life. Bill Tutt has written a couple of posts

re: Destroy: A new feature for Orcas

wxt2000 — Fri, 13 Apr 2007 17:37:03 GMT

I have a question about such scenario. I have created a source folder names $TP1/Lib1. Then I decided it was all wrong and i deleted it. Because my teammate is still waiting for this Library I created a new one with the same name. Right now I have sometimes problems with getting latest version. I would like to destroy the old folder while keeping the new one. How will I go about it?

Your answer will be extremely important to me, as I have many such folders on production server.

re: Destroy: A new feature for Orcas

Ted Holien — Sat, 19 May 2007 22:44:47 GMT

Will the Destroy option work even if the destroyed folders and files had participated in branch or merge operations with folders and files that are not destroyed? (Or will it only work on completely autonomous folders and files?) I would think that you had thought of these scenarios, but it would be nice to know whether there will be limitations in this regard.

I'm also unclear on what is meant by "content" vs. "non-content" data. Some clarification would be appreciated.

re: Destroy: A new feature for Orcas

tfsvcs — Mon, 21 May 2007 18:09:06 GMT

wxt2000: If you do a 'tf dir /deleted $/TP1' you'll notice a line that contains 'Lib1;X123'. If you want to destroy that item, you simply do: 'tf destroy $/TP1/Lib1;X123'.

Ted: Yes, destroy will remove folders and files that have participated in branching and merging.

By content, I mean the actual files content. Non-content data for a file's history are things like still showing up when you do a 'tf dir' (Source Control Explorer), 'tf history' command still showing those versions, or the file name still shows up in as beloning in a changeset.

Here's an example of what I mean:

echo blah > a.cs

tf add a.cs

tf checkin /i (This generates changeset 5)

tf edit a.cs

echo blah blah >> a.cs

tf checkin /i (This generates changeset 6)

If I want to keep the item around at changeset 6, but want to destroy all content (but not history) then I would do this:

tf destroy $/teamProject/a.cs /keephistory

So when you run the following commands changeset 5 will still show up:

tf history a.cs

tf dir a.cs;C5

tf changeset 5

However, since the file content for changeset 5 has been destroyed, trying the following will issue an error:

tf get a.cs;C5

On the flipside, if you had done 'tf destroy $/teamProject/a.cs' then the above commands would return "item not found" for a.cs all of the time.

Novedades en Visual Studio Team System 2008

Yo sólo pasaba por aquí pero ya que estoy.... — Wed, 05 Dec 2007 00:06:28 GMT

Como muchos ya sabréis hace poco Microsoft lanzó al mercado Visual Studio 2008. Si estáis