TFS. .NET and paths longer than 260 characters

June 19, 2007 at 11:18 pm | In Team Foundation Server |

Have you ever wondered why Team Build doesn’t support working folders with paths longer than 260 characters (MAX_PATH)?

Basically, the .NET APIs don’t support it because the Windows APIs don’t support it.

But it’s not as clear-cut as that. The Windows APIs support a workaround by prefixing the file name with “\\?\” - but .NET doesn’t support that.

For the whole story, have a read of these two articles from the BCL Team.

Unfortunately it looks like this one is around for a while until it gets fixed in Longhorn and .NET >3.5.

For the Team Build workaround, I tend to recommend you name your projects/solutions by their shortnames instead of their full namespaces.

Use:

$/TeamProject/Trunk/Component1/etc..

Instead of

$/TeamProject/Trunk/Company.Project.Component1/etc..

No Comments yet »

RSS feed for comments on this post. TrackBack URI

Leave a comment

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Blog at WordPress.com. | Theme: Pool by Borja Fernandez.
Entries and comments feeds.