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.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
5.How to get absoulte path from relative path?
Hi! Consider string containing relative path, may be with "\..\"and "\.\", with or without drive name, etc. I looking for API routine that converts that arbitrary filepath to full path, based on current drive, current directories on all drives and (bingo!) on any other filepath that is used as starting point. Example: starting point = "d:data\configs\conf1.txt", filepath = "..\images\img1.gif", result = "d:\current-directory\data\images\img1.gif" It should be something like FExpand function from Borland Pascal RTL and fnmerge() from POSIX API. Thanx in advance, Ilya
6. Converting absolute path to relative
7. There are any Path or Directory function to convert an absolute path to a relative path?
Users browsing this forum: No registered users and 54 guest