Tracker: Bugs
VS.NET allows you to define a solution configuration
that does not correspond to child project
configurations with the same name. For example, you
can define a solution configuration named 'Official'
that uses the 'Release' project configurations for all
of the member projects.
Nant assumes that each child project has a
configuration with the same name as the solution
configuration being built. The configuration I
described breaks this assumption.
I'm attaching a solution file that illustrates the
issue. I created a new solution and added two child
projects, named 'Aaron' and 'Gert'. I added a new
configuration to the solution called 'Official' without
corresponding project configurations. I then
deselected the 'Gert' project from the Official
configuration, so that Official will only build 'Aaron'.
Gert Driesen
Tasks
0.85
Public
Comment ( 1 )
|
Date: 2005-03-25 19:43 Logged In: YES |
Attached File ( 1 )
| Filename | Description | Download |
|---|---|---|
| NantTest.sln | A solution file where the solution and project configurations do not match | Download |
Changes ( 5 )
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2005-03-25 19:43 | drieseng |
| resolution_id | None | 2005-03-25 19:43 | drieseng |
| assigned_to | nobody | 2005-03-25 19:43 | drieseng |
| close_date | - | 2005-03-25 19:43 | drieseng |
| File Added | 85967: NantTest.sln | 2004-05-03 20:19 | dordon |
