nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Public bug reported:

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 binarly 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.

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


** Tags: feature

** Changed in: nunitv2
    Milestone: None => 2.6.0

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

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

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

** Tags added: feature

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

Title:
  Separate packaging of NUnit for .NET 1.1 and 2.0

Status in NUnit V2 Test Framework:
  Triaged

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 binarly 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.