Hi,
Here is my issue with VS.NET IDE project reference:
I have a project (myproj.csproj) referencing a non-GACed strongly named
assembly (comp.dll 2.0.1.0) with copy local = true; we also have a comp.dll
2.1.0.0 version GACed. when I close the project and reopen it, the reference
is still ok and point to the right version (2.0.1.0). BUT if I remove the
myproj.csproj.user and then re-open the project, the reference will be
changed by VS.NET IDE to 2.1.0.0 - this will cause a problem for our build
process because when the build master checkout this project file w/o the
myproj.csproj.user file and the reference to comp.dll will be changed to
newer version that exists in GAC. One way of solving this issue is to check
in the myproj.csproj.user (but this sounds wierd), any other good solution
or settings somewhere to force the .csproj to use hard reference such as
C:\VSS\Somewhere and not use the relative path such as "..\..\..\Somewhere"?
Thanks a lot!
John