Completed
Last Updated: 11 Apr 2020 12:18 by FredDavis
Ewin
Created on: 26 Feb 2014 20:35
Type: Bug Report
1
Path too long on backup problem
I had some issues with Test studio projects opening in VS.  I reported this issue to Telerik Support on Ticket ID 755261.  The main thing from the ticket to note is that the project would backup would throw this error:

[11/07 00:23:37,devenv.exe(6016:1),ProjectModel] Project.BackupProject() : EXCEPTION! (see below)
     Situation: Error creating project backup
     Outer Exception Type: System.IO.PathTooLongException
     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.
     HRESULT: 0x800700CE (Official ID (if app.) = 2147942606, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_FILENAME_EXCED_RANGE) 

With this in mind, I moved all automation projects' folder as close to my base C drive that I could instead of having it on my desktop with filepath of C:\users\name of user\folder... 

Even after moving my folders, I still had to shorten my automation folders to be a single folder deep and have my tests have shortened file name that I codified to make some sense to what the test should do.  I have this problem from R1 2013 and still have this issue.  

Though I am not sure if others have had this particular issue happen to them, I would think that this problem causes me as a user to lost the flexibility of having my projects in a convenient location on my computer instead of having to dig through to find it.  
7 comments
FredDavis
Posted on: 11 Apr 2020 12:18
Try to use Long Path Tool, it really can help you with that.
ADMIN
Daniel Djambov
Posted on: 10 Mar 2014 08:14
Telerik: we have now changed the backup to create an archive so this issue will no longer be valid. The build with the fix will be available in March 2014.
Ewin
Posted on: 27 Feb 2014 16:50
I put a link to this item in the ticket
ADMIN
Konstantin Petkov
Posted on: 27 Feb 2014 16:01
Please respond in the ticket you mean pointing to this feedback item. Thanks!
Ewin
Posted on: 27 Feb 2014 14:59
I think having the backup in zip instead of what is happening now is more useful.  But I am just checking if you truly the issue I am talking about.  

But what are your thoughts about the situation i had to go through to move my automation projects folder to a directory close to C: . I did not really like having to move my projects in the first place since there was a lot of hassle to move them there with the source control (I know there is a recent addition where dropping the source control, but that didnt exist when I was dealing with this).

if you have access to support ticket system, you could check out my screencast at the bottom of the ticket for VS-doing-a-random-backup-when-no-update-happened.zip. The file is 11mb.  
ADMIN
Konstantin Petkov
Posted on: 27 Feb 2014 07:21
Thanks, we are aware of the problem. We could actually wrap the backup in a .zip file since most of the time it isn't needed. We keep it just in case you can revert, but that should be done only if there is nothing we can do short term for a blocked customer.

How does that sound to you? Your feedback is much appreciated!
Ewin
Posted on: 26 Feb 2014 20:36
I meant to say that VS would attempt to backup even when TS is the latest build available.