Visual Studio - TFS - Editing assembly definition error - 259 characters

Question

I am trying to modify an existing assembly definition. I get the following error whenever I click on Process.

Team Foundation Error

TF400889 : The following path contains more than 259 characters. Specify a shorter path.

Answer 1

AFAIK you are pretty much full . Common workarounds are to shorten the build path on the server or, conversely, encourage developers to use the path to the local working directory, which is always at least as long as the working directory of the build server.

Answer 2

While you may not be able to change the long path to the file, there is a solution for you!

If you are like me, you probably created your build controller and then started to learn TFS Builds. So, you filled in the spaces something like this:

By default, this specifies the build path for accessing any custom assemblies your custom build process requires. If you do not have custom assemblies, you do not need this value.

To return to this dialog box, open the Team Foundation Administration Console on the build server and click Properties on the build controller. Just delete the path and your problem will disappear (or if you really have custom builds, point directly to this folder).

Answer 3

My problem with the accepted answer is that it mentions a fix for the build server. The original question is not about problems on the build server. In the screenshot you can see that this is the local path of AppData / Temp. He is trying to change the assembly definition from Visual Studio.

I ran into the same problem and found a job. The path that was a mistake for me was not even in the Source Settings workspace. After playing a little, I found that if you change something on the Source Settings tab and return to the Process tab, it will work. For example, on the Source Settings tab, click the "Status" column of the first empty column and change it to "Cloaked", then click this row, you will not notice that nothing has changed. But now you can return to the Process tab, and everything will be fine.

A tiny “change” should initialize something that the construction will determine the source that it draws. I am using Visual Studio 2013 and 2015.