TF10128 - Path contains more than the allowed 259 characters.

Mon, 22 Oct 2007 20:22:18 Z

In Orcase Beta2, I tried to do a check out today from Team Foundation Source Control Explorer and encountered this error:

We try to use the Microsoft assembly naming conventions so a given assembly might be have a lengthy path like

$(RootPath)

CT.Clients (Container)

CT.Clients.Query.Hierarchal (Container)
CT.Clients.Query.Hiercharchal.Exporters.Print (Project)

I assumed that TFS / Orcas used unicode paths so this would never been an issue. Java can have lengthy packages/namespaces so shouldn't TFS / .NET be able to as well?

What is the best way way to address this issue?

thanks!

scottm

TF10128 - Path contains more than the allowed 259 characters.

Tue, 23 Oct 2007 00:38:34 Z

Unfortunately, as far as I know the limitation is not going away in Orcas.

And the best way to address that would be to use shorter path (at the repository planning stage). Also you need to take care how you name your branches (as it might easily overstep the 260 boundary).

By the way, what do you mean by Microsoft assembly naming convention? I thought usually the idea is to make the folders according to the namespace:

$(RootPath) = CT

Clients

HierarchicalQuery

Exporters

Print

Cheers, Eugene

TF10128 - Path contains more than the allowed 259 characters.

Tue, 23 Oct 2007 01:52:59 Z

Thanks for the info. I guess its just frustrating as we never had this problem back in the old SVN / CVS - Java days.

TF10128 - Path contains more than the allowed 259 characters.

Wed, 24 Oct 2007 16:43:04 Z

The tough thing is that TFS tries to create a new folder in the TFS tree using the full project name. So if you have a long project/assembly name, you get a long folder name in TFS as well. You have to override this TFS naming behavior using the advanced button during initial checkin.

TF10128 - Path contains more than the allowed 259 characters.

Wed, 24 Oct 2007 16:46:23 Z

Overall, I would not use the naming schema you have outlined in your first post (even without repository issue). I'd say it is over-informative - one does not need the whole namespace at every single level of the hierarchy.

Cheers, Eugene