Bugs item #947214, was opened at 2004-05-03 16:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=947214&group_id=31650
Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: Aaron Witt (dordon) Assigned to: Nobody/Anonymous (nobody) Summary: Solution task assumes configuration names are the same Initial Comment: 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'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=947214&group_id=31650 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
