We have a fairly standard release procedure using Visual Source Safe to mark the assembly before it is released. This allows us to access from this label if there is any problem, and use it for branching if changes are necessary.
We have several different projects and always labeled using the build version number. for example "V1.0"
After moving some projects to TFS, we noticed that if you try to tag using the same version number as another solution, for example. Solution A and solution B release "V1.5", then TFS will not allow you to do this because the shortcut name is processed globally. After reading several blogs on this subject, which discusses how TFS tags are not a point in time, but a collection of files, I think we will need to start including the project name in the shortcut to get around this, for example. designate as "Project A V1.5" and "Project B V1.5". Does this sound like the right approach?
Hoody source share