Split Compact Framework 2.0 and 3.5 builds into separate solutions

Bug #1213180 reported by Charlie Poole
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnitLite
Fix Released
Low
Charlie Poole

Bug Description

Having both of these in the same solution requires manually controlling what is deployed each time a test is run. VS2008 works best for compact framework projects when there is just one framework target in the solution.

Related branches

Changed in nunitlite:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 1.0
Changed in nunitlite:
status: Triaged → Fix Committed
milestone: 1.0 → 1.0b2
Changed in nunitlite:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.