when nuget search for the config file to use, it seaches a file call nuget.config under solutionDir/nuget/ first and then in the parents directories.<br /><br />but it does not search for a config file in the nuget.exe directory.<br /><br />With the below directory structure : <br />----.nugetUpgrader<br />| NuGet.Config<br />| NuGet.exe<br />| NuGet.targets<br />| <br />----AppDir<br />| | AppDir.sln<br />| ----.nuget<br />| | NuGet.Config<br />----packages<br />| | repositories.config<br />| ----CommonServiceLocator.1.0<br />| | | CommonServiceLocator.1.0.nupkg<br />| | | <br />| | ----lib<br />| | ----NET35<br />| | | Microsoft.Practices.ServiceLocation.dll<br />| | | Microsoft.Practices.ServiceLocation.pdb<br />| | | Microsoft.Practices.ServiceLocation.XML<br />| | | <br />| | ----SL30<br />| | Microsoft.Practices.ServiceLocation.dll<br />| | Microsoft.Practices.ServiceLocation.XML<br />| | <br /><br /><br />when i used the following command line /.nugetUpgrader/nuget.exe install -solutionDir AppDir ...<br /><br />the file /.nugetUpgrader/nuget.config is not read, but it use the config file under AppDir/.nuget
Comments: @feever57 one thing we're thinking about is changing the logic so that rather than being hard-coded to look for a .nuget/nuget.config, we look for a nuget.config file that is a peer to the nuget.exe that was run. In the package restore scenario, then, the behavior would be consistent with what happens today (since the nuget.exe that is being run is in the .nuget folder). When executing nuget.exe from some other location, then the nuget.config in that location would be the one selected. In this world, though, it's an either/or proposition (.nuget/nuget.config or custom location nuget.config) depending on where nuget.exe was run from. Does that work for your scenario, or were you wanting both nuget.config files to participate?
Comments: @feever57 one thing we're thinking about is changing the logic so that rather than being hard-coded to look for a .nuget/nuget.config, we look for a nuget.config file that is a peer to the nuget.exe that was run. In the package restore scenario, then, the behavior would be consistent with what happens today (since the nuget.exe that is being run is in the .nuget folder). When executing nuget.exe from some other location, then the nuget.config in that location would be the one selected. In this world, though, it's an either/or proposition (.nuget/nuget.config or custom location nuget.config) depending on where nuget.exe was run from. Does that work for your scenario, or were you wanting both nuget.config files to participate?
