Separate packaging of NUnit for .NET 1.1 and 2.0
Bug #702734 reported by
Charlie Poole
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit V2 |
Fix Released
|
High
|
Charlie Poole | ||
Bug Description
Currently, versions of NUnit (except the Gui) are built twice, once using .NET 2.0 and once with .NET 1.1, and both sets
are included in the binary packages. In the case of the MSI, the 1.1 assemblies are an optional feature.
We want to have separate packages for the 2.0 and 1.1 builds, with appropriate names. The build script will need to be
modified to build and package them separately.
Related branches
| Changed in nunitv2: | |
| milestone: | none → 2.6.0 |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| tags: | added: feature |
Revision history for this message
| Charlie Poole (charlie.poole) wrote | #1 |
| Changed in nunitv2: | |
| status: | Triaged → In Progress |
| milestone: | 2.6.0 → 2.6.0b1 |
| description: | updated |
| Changed in nunitv2: | |
| status: | In Progress → Fix Committed |
| Changed in nunitv2: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It should be noted that for this to work the primary NUnit install (2.0 or higher) needs to know how to find the 1.1 install. Currently this is done by always putting the 2.0 and 1.1 binaries in sibling directories. For 2.6, we can still check some standard locations but to allow for different configurations, the locations of the binaries should be stored as a setting.