Repro steps :
1. Imagine user having a bunch of different solutions under C:\Sources.
2. In order to re-use packages across solutions, he provides "C:\Sources\Packages" folder as repository path in the Nuget.config file.
Expected:
Now on installing packages, I would except the Hint path in project references to be absolute path (C:\Sources\Packages) ,
Actual :
A relative path is added as HintPath.
Impact:
When the path is relative, it breaks when the projects are moved across solutions.
A related issue around this is discussed @ http://nuget.codeplex.com/discussions/400870.
Opening a separate issue as the current pull request seems to be handling only $(SolutionDir) scenario.
Comments: However, in cases of Nuget or shared packages, using an absolute path is preferred. It should be possible to add a reference path that can be used locally on many dev machines and the SCM build location.
1. Imagine user having a bunch of different solutions under C:\Sources.
2. In order to re-use packages across solutions, he provides "C:\Sources\Packages" folder as repository path in the Nuget.config file.
Expected:
Now on installing packages, I would except the Hint path in project references to be absolute path (C:\Sources\Packages) ,
Actual :
A relative path is added as HintPath.
Impact:
When the path is relative, it breaks when the projects are moved across solutions.
A related issue around this is discussed @ http://nuget.codeplex.com/discussions/400870.
Opening a separate issue as the current pull request seems to be handling only $(SolutionDir) scenario.
Comments: However, in cases of Nuget or shared packages, using an absolute path is preferred. It should be possible to add a reference path that can be used locally on many dev machines and the SCM build location.