title: Understanding Label limitations
body: <p>A <a href="http://iworkonsoftware.blogspot.com/2010/04/tfs-labels.html" rel="noreferrer">blog</a> states</p>
  
  <blockquote>
    <p>Labels come with a big warning though - labels themselves are not
    version controlled, meaning that there is no way to track or audit the
    history of activity on a label. Plus, labels don't keep copies of
    versions in case of a file deletion, so if a file gets deleted, any
    label that relies on a version of that file is essentially hosed.</p>
  </blockquote>
  
  <p>This is not the only place I've read similar information regarding TFS labels.  The lack of history is clear enough.  The second part "labels don't keep copies of versions..." is unclear.  In fact, I created a test project > labeled it > deleted a file > performed a Get by Label and the file came back.  So what is this referring to?  Has the label functionality changed in TFS as of recent?</p>
  
  <p>I realize that a file deletion does not actually remove history, is that the cause?  In other words, if I run</p>
  
  <blockquote>
    <p>tf destroy "$/MyTeamProject/Project/FileName.cs"</p>
  </blockquote>
  
  <p>Is that what it means to delete a file?  If so, that seems an extraordinary circumstance to even consider.  I mean, its an intentional unrecoverable deletion of history.  Changesets are not going to be any improvement over labels in such a case.</p>