Comments
2 comments
-
I suspect you are getting different results in XP vs. 7 because of the difference in the location of where the two operating systems store local app data.
XP: \Documents and Settings\$USER$\Local Settings
7: \Users\$USER$\AppData\Local
http://social.technet.microsoft.com/wik ... vista.aspx
This would explain why the specified path, file name, or both are too long in XP and not 7 because the XP path will be slightly longer than that of 7.
For the error "The specified path, file name, or both are too long".
We recommend you relocate your working base folder
http://documentation.red-gate.com/displ ... e+too+long
Note: The working base folder is different from the working folder.
http://documentation.red-gate.com/displ ... rking+base -
Hello..
I suggest you to try "Long Path Tool" program.
I have try it and its working on windows 7.
Add comment
Please sign in to leave a comment.
I have linked a database to a git working folder, and committed the objects on a Windows 7 machine with SSMS 2008 R2. Some of the unit test sprocs have quite long verbose names, with the longest path being 186 chars (filename is 134). All of these were committed fine. We use local dev VM's running Windows XP SP3 (low footprint) with SQL Server 2008 R2 Express Advanced. I installed source control 3.9 on here too, and linked the database to a clone of the repository. When I try and get the latest I get the following error message:
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
The longest path for the VM is shorter at 175 chars, way below the limits in the error message.
Having done some investigation, i can use any path length on the XP VM as long as the filename part does not exceed 114 characters. Is this a know issue when using the product with Windows XP?
Thanks
Niall