74 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• G commented  ·  June 5, 2013 10:11 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please fix this. It is hard enough getting the LAMP team to use TFS without trying to explain why they need to refactor their directory structures.

  Help!

• Anonymous commented  ·  May 28, 2013 9:56 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  thanks for the info.,you could also try long path tool. it helped me with

  error 1320 in Win 7.,:) ricktor

• Reinhard Kuhn commented  ·  May 27, 2013 11:50 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This relic of the DOS area has been an annoyance in 2010 - it is, even if slightly increased, an unforgivable shame in 2013!

• Tony Prudente commented  ·  April 30, 2013 12:07 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm a long-time TFS supporter, and this is my number one annoyance. I brought TFS to our company where there was some existing skepticism about it. It does not help my case when builds are failing because of a lame character limit that has nothing to do with Windows. MS stated that the reason for the 400 char limitation is because of index size limits in SQL server - which obviously means they need to make an alteration to how they're persisting/indexing the TFS data. So MS please get on it!!!

  http://blogs.msdn.com/b/bharry/archive/2012/09/12/visual-studio-update-this-fall.aspx

• Bartosz Bielecki commented  ·  April 26, 2013 3:20 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The year is 2013 and there is still no sign of Microsoft dealing with it. You either PInvoke half of WinAPI JUST to avoid .NET before-api-calls that check for the length of normalized path, or external libraries (which basically did all the things for you).

• Anonymous commented  ·  April 25, 2013 9:35 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is one of the most frustratingly moronic legacy problems to still have around.

• Anonymous commented  ·  April 24, 2013 8:59 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  To have any limits on path length is stupid. I remember when computer languages routinely had limits on the names of variables.

• Dave commented  ·  April 5, 2013 9:35 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is ridiculously annoying! Please allow for long file length. The TFS 2012 increase to 400 is ok, but not ideal. Get with the 21st century!

• Xian Sembrano commented  ·  April 1, 2013 9:00 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  why not used third party apps like "long path tool" ? which can be helpful, it helped me out a lot. maybe, it can help you also.

• Lars Johannesson commented  ·  March 22, 2013 7:46 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We currently have some code in SVN and some in TFS. Initially we planned on moving the svn code to TFS but this bug made us reconsider and instead we will be migrating away from TFS.

• Lee Hull commented  ·  February 28, 2013 6:52 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  VERY VERY annoying, least give a way to remove them from TFS without downloading them so we can at least fix it.

• Paul commented  ·  February 27, 2013 3:51 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We've been hit with this issue many many many times and would like to see it resolved. This issue very frustrating and is causing our teams wasted effort as we are transitioning from other ALM systems to Microsoft's ALM system.

• Rocky commented  ·  February 25, 2013 9:14 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Here's a good way to get around the TFS developers refusing to upgrade their software to use an API that was developed in this century:

  http://praphullaparab.wordpress.com/2010/08/12/tfs-2010-error-tf205022-path-contains-more-than-the-allowed-259-characters/

• Anonymous commented  ·  February 23, 2013 8:45 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hello, wake up MS. It's 2013 now and still can't have a long file path without limitations.

• J commented  ·  January 18, 2013 3:12 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We run into this issue constantly too. This need to be fixed so that we can organize our solution folders without this stupid restriction

• Chris F commented  ·  January 16, 2013 8:27 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We run into this issue CONSTANTLY. It makes me want to pull my hair out. I don't care about backwards compatiblity. If this was fixed...truly fixed...not the 400 characters that are now available with update 1....as in I can have 32768 Characters I'd upgrade to the next version that had this feature in a heart beat.

  Is there any hope this is going to get addressed?

• Woody commented  ·  January 14, 2013 2:22 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As users we should get an update more than once every three months that doesn't provide a roadmap for solution. Otherwise, what is the point of this site?

• colin dooely commented  ·  January 14, 2013 5:57 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I hate this phrase, but I'll use it anyway. OMG. However, to all hoping to have this fix. Think about all the issues regardsing backwards compatibility that an update to this would cause. An expensive one to maintain and probably not going to happen. Subversion all the way?

• Siva commented  ·  January 11, 2013 10:40 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  do we have any solution yet?

• Anonymous commented  ·  January 9, 2013 7:50 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please fix it, it is annoy!