Run configuration problems
There is an element inside the runconfig file called
relativePathRoot. This value holds the path to the solution root, so that other paths inside this file can be relative. When executing tests from within the IDE this value is getting reset properly for the machine the solution is opened on.
On my automated build server I am building the solutions and executing the tests from the command line, and apparently when you execute tests using MSTest.exe from the command line this value is NOT getting reset to the path to the solution on my server.
Is there a way to get MSTest (from the command line) to reset this value properly?
Thanks.
[698 byte] By [
NewDawn] at [2007-12-16]
There have been a number of changes sperifically related to this attribute -- we now have removed it. It is best to remove this element from the Run config, and then just involve MSTest from the solution directory (or the directory you want your paths to be considered relative to)
a) If I remove this element, and then subsequently edit the runconfig from the IDE (Beta 2) will it put the element back in there?
b) If I'm executing MSTest from something similar to a shortcut, will filling in the Working Directory with the path to the solution directory be what you're talking about, to get it to invoke from the solution directory?
Thanks.
a) Yes, I think it will put the element back. My suggestion is that you just ignore this element and do not use it. Thus when you get the 2005 final release, run config would still work for you.
Leo Huang
Dev, VSTS
Leo Huang wrote: |
| a) Yes, I think it will put the element back. My suggestion is that you just ignore this element and do not use it. Thus when you get the 2005 final release, run config would still work for you. Leo Huang Dev, VSTS |
|
Well, the problem with that is we have different paths to solutions between development workstations and my build server. So I can't exactly ignore it.
What I did is create a quick little utility that opens this runconfig file and replaces the path in this element to one that is passed in via command line parameters to this utility. My build server is calling this utility for every solution before it executes MSTest for it. This works for now.
Thanks.