I'm trying to write a relative path from a file but the only relative paths I can get are from the running app file.
This is causing problems as NCrunch runs its test from a different directory so its failing all my tests because it cant find the files which are relative to my code file.
It's important that this be a relative path as there are several people working on this project so absolute paths don't work.
Is there any way to make the path relative to the .cs file where the code is written?
until now I've been using
private static readonly string MyDocumentsRoot = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments);
public static readonly string ApplicationRoot = MyDocumentsRoot + #"\Visual Studio 2012\Projects\";
but really need it to be a little more relative
The solution is well documented in NCRUNCH documentation:
Implicit File Dependencies
The other solutions, sooner or later, will fail. (I had similar trouble with MSTest, which offers a similar solution).
You can try with this code - based on GetExecutingAssembly method
string path = System.Reflection.Assembly.GetExecutingAssembly().Location;
string directory= Path.GetDirectoryName( path );
Or
string path = System.Reflection.Assembly.GetAssembly(YourClass).Location;
The documentation shows the paths are relative to the project file:
For example, you could specify the following files to include:
SpecialConfiguration\ImportantConfigFile.config
..\CustomBuild\**.*
..\..\TestResources\Spreadsheets\*.xls
This would include an individual file (ImportantConfigFile.config), the entire contents of the ..\CustomBuild directory, all of its subdirectories, and all .xls files within the ..\..\TestResources\Spreadsheets directory.
All file paths must be specified relative to the project file's path on disk. When NCrunch builds a workspace, it will automatically arrange all dependent files so they exist with the same relative paths in their workspace as they did in their original location.
You can use str=Directory.getdirectory which will give you the path of the app (the folders up until Release or Debug (where your app is located) and save it in a string (the method returns a string). After doing that you can use the str.replace(str1,str2) method which locates str1 and replaces it with str2. Just don't forget that \ inside a string is \\ because \ is an escape character. If you need help with escape characters let me know so I can help you with that as well.
I usually place an old style ini-file where my executable resides. Here I store the absolute paths of files and folders required by the application. This also enables me to configure these pathes differently in a production enivronment (on the cutomers site) than on my development environment. Having just a copy of this ini-file in the folder from where NCrunch runs the assemlies would solve the problem.
My ini-file implementation searches all the folders, starting at the folder where the executable resides, towards the root folder, until it finds the ini-file. This enables me to have different executables using a common ini-file. E.g. if a place the ini-file in the bin folder both, the Debug and the Release version will automatically access the same ini-file.
Related
I'm trying to find a file in a settings folder in my application. I have a xml file there. When I run the following code:
XDocument xDoc = XDocument.Load(#"..\settings\Settings.xml");
I get the DirectoryNotFoundException and the exception says not found at \bin\settings\Settings.xml'., instead of above. I even tried the full root directory to see the issue, C://... but it still includes a bin folder?
How can I have it so it doesn't include the bin part?
By default, the build results in Visual Studio are saved in a folder like bin\Debug. Since you use a relative path that jumps one folder higher, you get yourProjectFolder\bin\settings\Settings.xml. That file doesn't exist, since it's presumably in the project folder, not the bin folder.
The typical way to deal with this is to make sure the files that are supposed to be a part of the content actually have Build Action set to Content.
Using a rooted path definitely works - most likely, you made a mistake somewhere; either the path isn't rooted at all, or you're doing something like interpreting the path as an URI rather than a file path. XDocument.Load takes a URI, not a file path - the proper way to reference an absolute path on the filesystem would be file://C:/ThePath/Settings/Settings.xml.
In my nunit test project I have a layout like:
/Fixters/someFile.txt
/Services/SomeService.cs
someFile.txt is a file that I need to read as it contains text that I use for my unit tests.
How can I reference this folder without hard coding the path as other team members may store this project at a different path that me.
If you do File.ReadAllText(filepath) and any other equivalent method where you pass in a relative path, the runtime will use the app's current working directory to create the whole path. So generally speaking, you should be fine using relative paths. You might also need to specify that someFile.txt gets copied to the output directory.
If unsure what the cwd is, try Directory.GetCurrentDirectory()
I am working on a media player in C# but when I want to make my test I have a problem.
I have to create a new object song with the following path:
#"C:\Users\Jesus Antonio\Desktop\JukeboxV2.0\JukeboxV2.0\Datos\ich will.mp3"
It works but when I change the computer I have to rewrite the entire path,
My project is called JukeboxV2.0
In java I remember you can just write the path for example
#"JukeboxV2.0\JukeboxV2.0\Datos\ich will.mp3"
This will save a lot of time because I can take my project to different computers and it works, but here I don't known how to do that, anyone know?
You would do something like this to get the path "Data\ich_will.mp3" inside your application environments folder.
string fileName = "ich_will.mp3";
string path = Path.Combine(Environment.CurrentDirectory, #"Data\", fileName);
In my case it would return the following:
C:\MyProjects\Music\MusicApp\bin\Debug\Data\ich_will.mp3
I use Path.Combine and Environment.CurrentDirectory in my example. These are very useful and allows you to build a path based on the current location of your application. Path.Combine combines two or more strings to create a location, and Environment.CurrentDirectory provides you with the working directory of your application.
The working directory is not necessarily the same path as where your executable is located, but in most cases it should be, unless specified otherwise.
Path.Combine(AppDomain.CurrentDomain.BaseDirectory, #"JukeboxV2.0\JukeboxV2.0\Datos\ich will.mp3")
base directory + your filename
I was facing a similar issue, I had a file on my project, and wanted to test a class which had to deal with loading files from the FS and process them some way. What I did was:
added the file test.txt to my test project
on the solution explorer hit alt-enter (file properties)
there I set BuildAction to Content and Copy to Output Directory to Copy if newer, I guess Copy always would have done it as well
then on my tests I just had to Path.Combine(Environment.CurrentDirectory, "test.txt") and that's it. Whenever the project is compiled it will copy the file (and all it's parent path, in case it was in, say, a folder) to the bin\Debug (or whatever configuration you are using) folder.
Hopes this helps someone
Prologue - If i append PATH environment variable in windows with Installation Directory path of my application, i don't need to CD to installation directory to execute it.
Question - Would relative file path(s) in my application interpreted according to current execution path in console or according to installation directory. Strangely, in my application, the paths are being interpreted relative to current execution path, thus causing exceptions (File not found, etc).
Please help me out.
Relative paths will be interpreted relative to Environment.CurrentDirectory.
It will default to the directory where the process started in, but can be changed.
The behaviour you are encountering (relative pathes being evaluate in the context of the current working directory) is by design.
If you want to always place a file next to the currently executing assembly, this piece of code might come in handy:
public static string GetPathRelativeToExecutingAssemblyLocation(string aRelativePath)
{
return Path.Combine(
Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location),
aRelativePath);
}
Say I have this file structure
Soultion-> Folder1 -> FileIwant.html
So this could be something like C:\Soultion\Folder1\FilterIwant.html
Now I need to read this file into my application. I can't just hardcode it since when I give it to someone else they might put it on F: drive or something.
Or when I create a msi file the path might be completely different. So how can I say maybe take
"Folder1\FilterIwant.html"
and use that to get the folder path regardless of where they put it?
Edit
I tried Path.GetFullPath but I land up in the bin/debug directory. But my file is not in that directory. I think it is a couple directories before. Also if I make a msi file will I have bin/debug directory?
Why is a file which is used as part of your application not in the same folder as the application? It sounds to me like you should set the properties on that file to copy to the output folder when you do a build.
Doing that will make sure your file is in the bin\debug folder.
EDIT:
either that or you should be placing your files in one of the special folders, app data or my documents spring to mind.
When Visual Studio compiles your project, it will be putting the output into the bin\debug directory. Any content files that you want to reference must also be copied to those locations, in order for your app residing in that directory to be able to read that file.
You have two choices:
either you set the Copy to Output Directory property on your FilterIwant.html to Copy if newer; in that case, if the file has changed, it will be copied to the output directory, and you should be able to reference it and load it there
or
you just define a path in your app.config, something like DataPath, and set it to your folder where the file resides. From your app, you then create the full path name for that file as Path.Combine(AppSettings["DataPath"], "FilterIwant.html") - with this approach, you become totally independant of where the file really is and you don't need to move around anything. Also: this gives you the opportunity to create an admin/config utility for your users later on, so that they can pick any directory they like, and your app will find those files there.
In my console app, I started with the debug directory until i found the closest parent folder I wanted.
static void Main(string[] args)
{
Console.WriteLine("Start");
var debugDir = Environment.CurrentDirectory;
DirectoryInfo di = new DirectoryInfo(debugDir);
var searchDir = "";
while (!di.FullName.ToLower().EndsWith("Folder1"))
{
if(di.FullName.ToLower().EndsWith(":")) //if you went too far up as in "D:" then
break;
di = di.Parent;
}
Console.WriteLine(di.FullName);
}
You need the help of System.Io.Path class:
GetFullPath: Returns the absolute path for the specified path string.
Edit:
You might also need the application directory - this is where your application will be installed:
string appPath = Path.GetDirectoryName(Application.ExecutablePath);
Path.GetFullPath
Edit
The bin/Debug path will not be present when you run your installed application (unless you specifically tell the installer to use that subdirectory, of course).
You probably want to pass the full path as a command line argument. You can then get the argument using the args parameter of the Main method. To convert a relative path to an absolute one you can use Path.GetFullPath:
using System;
using System.IO;
public class CommandLine
{
public static void Main(string[] args)
{
// The path is passed as the first argument
string fileName = arg[0];
// get absolute path
fileName = Path.GetFullPath(fileName);
// TODO: do whatever needs to done with the passed file name
}
}