Currently when resolving the path to the referenced DLL in the project file a relative to the project in the solution path is created and placed into the hint path. While this is fine for projects that live in a single solution or within multiple solutions where the solution files are in the same directory, if the project is used in multiple solutions where each solutions directory could be at a different relative path than the others having the "..\packages" style path will cause the reference to be not found in other solutions.
Currently to solve this issue I manually edit the reference's hint path in the project file to look something like this:
<HintPath>$(SolutionDir)\packages\Library\lib\library.dll</HintPath>
I downloaded a copy of the source and looked at attempting to do a string replace but it appears that the object being used to add the reference looks at the above as an invalid URI. After seeing that issue in my attempt to propose a fix I am unsure if what I'm proposing above is correct syntax. I can state that under MSBUILD in VS2012 and TFS2012 it works without issue.
Comments: Is there another way to achieve the same result? This is generally a bigger issue with our packages that are pulled from our local feed server. I had thought of updating those packages so that they utilized a powershell script to alter the hintpath. Obviously this wouldn't work for those packages that were pulled from the offical server. After I posted this I saw that there may be some issues/features that have received some votes that could offer a similar solution. Would it be plausible to expect some sort of future functionality to mitigate the issue I mentioned in the OP?
Currently to solve this issue I manually edit the reference's hint path in the project file to look something like this:
<HintPath>$(SolutionDir)\packages\Library\lib\library.dll</HintPath>
I downloaded a copy of the source and looked at attempting to do a string replace but it appears that the object being used to add the reference looks at the above as an invalid URI. After seeing that issue in my attempt to propose a fix I am unsure if what I'm proposing above is correct syntax. I can state that under MSBUILD in VS2012 and TFS2012 it works without issue.
Comments: Is there another way to achieve the same result? This is generally a bigger issue with our packages that are pulled from our local feed server. I had thought of updating those packages so that they utilized a powershell script to alter the hintpath. Obviously this wouldn't work for those packages that were pulled from the offical server. After I posted this I saw that there may be some issues/features that have received some votes that could offer a similar solution. Would it be plausible to expect some sort of future functionality to mitigate the issue I mentioned in the OP?