Thanks for the response Jeff, That gave us some better information to base our decisions on. I think we'll likely go with the relative paths. However, while I was validating the working directory I noticed some confusing behavior. When I changed the working directory and saved the project file (.gallio) in Icarus, the working directory didn't immediately take, I had to close the project and re-open it to get it to use the new working directory.
As I don't think we'll be taking advantage of this feature right now, it's not of concern for me, but I was curious if that was intended behavior or not? Thanks again. Mike Brown On Sep 18, 3:06 am, "Jeff Brown" <[email protected]> wrote: > Gallio sets the application base directory and working directory to the > directory that contains the test assembly, by default. > > You can change these. > > It's best to leave the appbase alone (so that other assemblies can be > loaded) but you can set the working directory to whatever you like. The > hint directories are just extra directories to look in for referenced > assemblies so they're not too relevant to this discussion (unless you mess > around with the appbase). > > Just the same, I recommend that you stick to the default behavior and just > keep using "..\.." prefixes on your paths. The nice thing about Gallio is > that it guarantees that those relative paths are valid (unless you change > the default settings in some way). > > For my own projects, I tend to change the output directory for Debug and > Release builds to just be "bin" instead of "bin\Debug" and "bing\Release". > Then my relative paths just look like ".." and I don't have to worry about > the build configuration changing where files get compiled. > > Jeff > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of Dev Mike > Sent: Thursday, September 17, 2009 10:48 AM > To: MbUnit.User > Subject: MbUnit Affecting assembly relative paths > > Greetings, > > We're trying to create our tests so that we use relative filepaths, > generally speaking these paths are relative to the bin\Debug folder, so we > either have to include "..\..\" or we have to copy our test data to the > output directory. > > I noticed that Icarus has a few values to set which sound like what I am > looking for, but I've been unable to use them. > > So, what are the purposes of: > > - Application base directory > - Working directory > - Hint directories > > My hope was that he host test runner could run the assembly from an > alternate path, preferably the location of it's csproj file, so that our > relative paths could be short, sweet, and immediately understandable. > > Thanks for any help. > > Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en -~----------~----~----~----~------~----~------~--~---
