Udostępnij za pośrednictwem

/map marks the spot

  • Artykuł

Now that you've had a bit of time to play around with Beta 2, I'm curious what people think of the mapping and cloaking funcitonality of Team Foundation source control. Do you set up multiple maps? Have you cloaked anything? How do you think the average user will set up working folders for their workspace? Any other comments about maps and cloaks in general?

Also, if you have a moment, I'm still interested in any comments on the process checkin and editting submitted changesets.

Comments

  • Anonymous
    May 10, 2005
    I am not using /cloak yet but I can imagine that as we create branches for each release (perhaps even milestone) that developers won't want the source code for every release (branch) in their workspace. That is how I'm anticipating using it. Of course the other way is to map $/ to C:Projects and then cloak unwanted team projects (I don't think I would use the product this way).
  • Anonymous
    May 10, 2005
    Thanks Keith! Out of curiosity, do you currently map $/, a Team project, or something else?
  • Anonymous
    May 10, 2005
    I'm mapping $/<MyProject> to C:Projects<MyProject>. I started out mapping $/ to C:Project but then I accidentally created folders under $/ which I don't think is a good idea. I've heard that by RTM TF won't allow anything but TeamProject folders at the root of the repository. I think that is a good idea.
  • Anonymous
    May 16, 2005
    Visual Studio Team System

    The big news around Team System at the moment is the announcement on Rick...