Just wondering what is really going on under the covers here, as I have a nuget.config file with specific values as follows, which appears to be respected and work fine when the MSBuild steps are occuring, but not in the earlier Nuget fetch packages step.
The NuGet.config, which is stored in a .Nuget child folder of the solution folder and contains
<?xml version="1.0" encoding="utf-8"?>
<add key="disableSourceControlIntegration" value="true" />
<add key="repositoryPath" value="$\..\..\..\NuGetPackages" />
As the Nuget step starts it reports the following. The part I'm concerned about is the \packages part where a completely different folder path from the request folder and path ($..\..\..\NuGetPackages) is generated on the fly.
[Step 1/7] scan: Searching for nuget.config files
[14:49:21][scan] Found packages folder: C:\TeamCity-BuildAgent\work\Core\IG\packages
I believe the folder should instead be something like (albeit fictionaly at this stage)[14:49:21][scan] Found packages folder: C:\TeamCity-BuildAgent\work\Core\NuGetPackages note: that once the MSBuild steps have finished, the NuGetPackages does get created, but only after the packages folder is created during the Nuget Fetch stage.
Is there anything I can do to help the custom repositoryPath be respected during the Nuget Fetch stage?