nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Public bug reported:

The project editor requires the configuration file to be specified as a
file name only, so it must always be located in the ApplicationBase
directory. This is usually OK but is inconvenient in some scenarios. We
should remove the limitation and allow an absolute or relative path to
be specified.

** Affects: nunitv2
     Importance: Medium
     Assignee: Charlie Poole (charlie.poole)
         Status: Triaged

** Changed in: nunitv2
       Status: New => Triaged

** Changed in: nunitv2
   Importance: Undecided => Medium

** Changed in: nunitv2
     Assignee: (unassigned) => Charlie Poole (charlie.poole)

** Changed in: nunitv2
    Milestone: None => 2.6.1rc

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1023058

Title:
  Remove limitations on location of ConfigurationFile in project editor

Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  The project editor requires the configuration file to be specified as
  a file name only, so it must always be located in the ApplicationBase
  directory. This is usually OK but is inconvenient in some scenarios.
  We should remove the limitation and allow an absolute or relative path
  to be specified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1023058/+subscriptions