Long Path Tool is useful also for developers

One of developers complainted about his last debug session:

“During a build on the server, because the location of the build is different than on DEV machine, I am getting the following error:

MyProj : error PS0099: Unhandled exception (2.2.4.45, 32 bit, CLR 4.0, Release): System.IO.PathTooLongException: 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. [C:\Project\DEV – AIP – Services DataRata\Sources\DEV\AIP\Services DataRata Mainline\DataRataService\Affinity_Rate\Affinity_Rate.csproj]
MyProj: error PS0099: at System.IO.PathHelper.GetFullPathName() [C:\Project\DEV – AIP – Services DataRata\Sources\DEV\AIP\Services DataRata Mainline\DataRataService\Affinity_Rate\Affinity_Rate.csproj]
MyProj: error PS0099: at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength) [C:\Project\DEV – AIP – Services DataRata\Sources\DEV\AIP\Services DataRata Mainline\DataRataService\Affinity_Rate\Affinity_Rate.csproj]

Long Path Tool can solve it

-->