Long path

Thomas Linder Puls · Post by **Thomas Linder Puls** » Tue Sep 28, 2004 3:32 pm

One of us suddenly geta lot of errors like this:

[28-09-2004 20:56:23] Local file update for $/_Vip7/share/Tests/Language implementation/Classes/Compiler/Syntax/Tests for construction of inside part of class, interface, implement or monitor/Tests for resolve section/Tests for interface resolution/test_06_2.prc failed: System.IO.PathTooLongException: The path is too long after being fully qualified. Make sure path is less than 260 characters.
at System.IO.Path.nGetFullPathHelper(String path, Char[] invalidPathChars, Char[] whitespaceChars, Char directorySeparator, Char altDirectorySeparator, Char volumeSeparator, Boolean fullCheck, String& newPath)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at VaultClientOperationsLib.WorkingFolder.BackupFile(String filename)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, Boolean makeBackups, OverwritePrompt PromptData)
at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, OverwritePrompt PromptData)
at VaultClientOperationsLib.UpdateThread.ProcessCommand(UpdateThreadCommand command, UpdateThreadCommandResult& outputResult)

What is the problem?

The path is 220 characters (i.e. <260).

Is there a limit of 260 chars?

Post by **jclausius** » Tue Sep 28, 2004 3:42 pm

Unfortunately, there is a 260 limit within the .Net Framework.

See this Usenet Post for more information.

Post by **jeremy_sg** » Tue Sep 28, 2004 9:18 pm

The path length that is probably overflowing is the disk path, not the repository path.

Post by **jclausius** » Tue Sep 28, 2004 9:26 pm

Thanks Jeremy. I should probably clarify a little -

When accessing disk, Vault client uses .Net FileInfo and PathInfo objects. These classes have the 260 character limit.

Thomas Linder Puls · Post by **Thomas Linder Puls** » Wed Sep 29, 2004 1:41 am

The working folder for $ is "C:\Arbejde\_Vip" so that does not add up to 260 characters.

I wonder if you use the "C:\Documents and Settings\thomas\Application Data\SourceGear" folder. Because then it is more likely that we get into problems.