why relative hint path but absolute reference path
by gerry » Fri, 24 Sep 2004 00:33:02 GMT
I have a vs.net 2002 solution that contains a number of projects
All projects are created in folders under the solution folder.
The idea here is that this entire solution should be 'moveable' ie. copied
to and useable from a new directory or computer.
And it almost is.
One project makes reference to an existing .net dll that also exists in a
folder under the solution folder.
The project file shows a relative hint path to the dll ie
"..\..\dllFolder\my.dll"
If I move the solution to a new folder and the open solution from the new
location, the dll can no longer be found. if i restore the original
solution folder, the dll is once again found. so obviously, although the
project file includes a relative hint path, vs.net is in fact looking for
the dll at an absolute location. This is causing headaches as this solution
cannot be 'passed around' without re-adding the reference to this dll.
is there some setting somewhere to get the relative path used ?
there does not seem to be any problem using relative project references - is
there some trick using a dummy project to get this to work ?
gerry
RE: why relative hint path but absolute reference path
by v-phuang » Fri, 24 Sep 2004 17:44:38 GMT
Hi,
I reviewed the thread and find that there is a similar issue in the
newsgroup below.Now our colleague has replied to you, you may go and take a
look.
Subject: why relative hint path but absolute reference path
Newsgroups: microsoft.public.vsnet.ide
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
Similar Threads:
1.why relative hint path but absolute reference path
I have a vs.net 2002 solution that contains a number of projects
All projects are created in folders under the solution folder.
The idea here is that this entire solution should be 'moveable' ie. copied
to and useable from a new directory or computer.
And it almost is.
One project makes reference to an existing .net dll that also exists in a
folder under the solution folder.
The project file shows a relative hint path to the dll ie
"..\..\dllFolder\my.dll"
If I move the solution to a new folder and the open solution from the new
location, the dll can no longer be found. if i restore the original
solution folder, the dll is once again found. so obviously, although the
project file includes a relative hint path, vs.net is in fact looking for
the dll at an absolute location. This is causing headaches as this solution
cannot be 'passed around' without re-adding the reference to this dll.
is there some setting somewhere to get the relative path used ?
there does not seem to be any problem using relative project references - is
there some trick using a dummy project to get this to work ?
gerry
2.Get machine name path from relative or absolute path
Hello, is it possible in C#.Net to get a path to a file in the form
"\\Spain\Madrid\readme.txt" from a relative path i.e "readme.txt" or
from a absolute path in the following form "C:\Madrid\readme.txt" where
"Spain" is the name of the machine that the file is on? Thanks in
advance.
3.absolute path to relative path conversion
4.Absolute or Relative path?
5.Relative & absolute path question (JavaScript, mostly)
6. User controls --> Relative/Absolute Paths
7. Absolute url from relative path
8. Absolute and relative paths in applicaiton