Remove limitations on location of ConfigurationFile in project editor
Bug #1023058 reported by
Charlie Poole
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit Project Editor |
Triaged
|
Medium
|
Charlie Poole | ||
| NUnit V2 |
Fix Released
|
Medium
|
Charlie Poole | ||
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.
Related branches
| Changed in nunitv2: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| milestone: | none → 2.6.1rc |
| Changed in nunit-project-editor: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in nunitv2: | |
| status: | Triaged → Fix Committed |
| Changed in nunitv2: | |
| status: | Fix Committed → Fix Released |
| Changed in nunit-project-editor: | |
| milestone: | none → 0.9.1 |
| assignee: | nobody → Charlie Poole (charlie.poole) |
Revision history for this message
| Charlie Poole (charlie.poole) wrote | #1 |
| Changed in nunit-project-editor: | |
| milestone: | 0.9.1 → none |
| status: | Triaged → Won't Fix |
| Changed in nunit-project-editor: | |
| status: | Won't Fix → Triaged |
| tags: | added: github |
To post a comment you must log in.
Moved to https:/