This is a migrated thread and some comments may be shown as answers.

Project references path - Test Studio vs. Command Line

5 Answers 40 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

David asked on 08 Nov 2012, 07:38 PM

We have a helper .dll that we recently wrote. We put it in a shared location relative to the projects that will be referencing it:

    \team1
       \project1
       \project2
   \team2
       \project1
   \shared
       \bin
           TestHelper.dll

When you add a reference to the .dll from the project settings, the reference gets added as a relative reference like this "..\shared\TestHelper.dll". The project reference works well and we can reference classes in the .dll - good stuff.

We have a problem though, when we try to run test lists from that project in our continuous integration environment (i.e., from the command line) - compilation errors complaining TestHelper.dll can't be found. What we found was that we need to change the project reference to go up one more directory level, like this "..\..\shared\TestHelper.dll".

The problem is we have to edit the XML by hand to add the extra level and when we do, it breaks the Test Studio project - it now gets the compilation errors. We can leave references to both in the project, but that is messy and difficult to communicate to the users (we have a lot of them).

Anybody else seen this issue - any suggestions? I tried to add the "root=" option to the command line, but no luck.

5 Answers, 1 is accepted

Accepted