Philip O'Gorman I ran into that issue too, are you running IIS as a reverse proxy? Try setting the allow double escaping (Go to Request Filtering, go to Edit feature settings and tick the checkbox). That fixed it for me.
What is still a problem though is building branches with a slash using msbuild.
I've been searching and searching, but can't find a solution. I've got a pipeline script running my build. The develop branch builds fine, but now I have a Release/188.8.131.52-hotfix branch. This is what happens (among others):
C:\Jenkins\workspace****\Releases%2F184.108.40.206-hotfix*******.csproj" (default target) (3:3) ->
(CoreCompile target) ->
CSC : error CS0006: Metadata file 'C:\Jenkins\workspace*****\Releases/220.127.116.11-hotfix\packages\Autofac.4.0.1\lib\net45\Autofac.dll' could not be found [C:\Jenkins\workspace\*****\Releases%2F18.104.22.168-hotfix\*****\*****.csproj]
CSC : error CS0006: Metadata file 'C:\Jenkins\workspace*****\Releases/22.214.171.124-hotfix_references\CookComputing.XmlRpcV2.dll' could not be found [C:\Jenkins\workspace\*****\Releases%2F126.96.36.199-hotfix\*****\*****.csproj]
Some of the build goes fine... it checks out the code, it does the nuget restore, but during the build inside msbuild it changes the encoding back and voila there is the slash again... So when is this encoding stuff finally being fixed? Just replace the special characters on the disk. Somewhere it says that you do, but it really doesn't happen...
I need that encoding gone in my folders it suits no purpose and doesn't make it more readable either.