I know that there is currently limit on the max file path in TFS 2010, and honestly, I can't believe this limitation still exists! It's the year 2010 and we're using Windows 7 with VS and TFS 2010, with 64-bit hardware and software. Why on earth
is this limitation from like 1995 still in place?!? Anyways, sorry for that short rant, I am just very frustrated over this.
We use feature branches at our office, and have a very large solution (around 450 projects separated between 2 VS solutions). Obviously, to keep everything in a nice logical, easy to understand format, we end up with a namespace hierarchy that is several
layers deep, which leads to folders that are also several layers deep, creating very long file paths.
When trying to Get Latest on a feature branch of ours, we are getting errors such as:
TF205022: The following path contains more than the allowed 259 characters: C:\dev\TFS\RQ4TeamProject\Dev\RQ4\FeatureBranches\PP_DuplicateDetection\Code\IQ.Enterprise.Integration.Windmobile.ApplicationServices\Service References\Intec\IQ.Enterprise.Integration.Windmobile.ApplicationServices.Intec.ProdInstServiceRetrieveData.datasource.
Specify a shorter path.
The case above isn't so bad since the error message actually told us the problem; that the file path is too long. We've had several developers waste days trying to figure out why our solution would build on our local machines, but not on our build
server. The only error message we would receive was, "cannot find reference to assembly X". As it turned out, the build server plopped all of the files into a root folder whose path was about 15 characters longer than on our local machines,
so assembly X was never being built because its file path was too long, and hence it couldn't be found.
Our solution to this so far has been to go in and start renaming namespaces and assemblies and the like to try and shorten their names, which works, but is a real pain. And as our solution continues to grow, it's going to lead to more obscure and unclear
namespaces, making our code harder to understand.
Is there some other solution to this file path limit that I am not aware of? And are there any plans to address this issue in future versions (I sure hope so)?
- Dan - "Can't never could do anything"