Hi all,

Is there a way to have NAnt skip "unused" project references (without attempting to build those projects on a given configuration) when a solution is being built on a certain configuration (debug/release)?

For instance, if "Project_1" is referenced by "Project_2" and I would like to have "Project_1" built on the debug configuration only, how should I instruct NAnt (by using the <solution> task) to skip "Project_1" (and "ignore" its reference in "Project_2") when building the release version of "Project_2"? I should mention that "Project_1" does not have a release configuration within the solution because I removed it from the Configuration Manager, in Visual Studio 2003.

To summarize things: I would like to get the output of both projects when building the Debug configuration and the output of "Project_2" only, when building the Release configuration. All code in "Project_2" that uses the reference to "Project_1" has been surrounded by "#ifdef DEBUG ... #endif" clauses to make sure that it's not compiled on the Release configuration.

Apparently, Visual Studio .NET 2003 handles this scenario gracefully by skipping "Project_1", while NAnt displays an error message stating that "Solution configuration 'Release' does not exist for 'Project_1'". I tried different things to solve this issue, but unfortunately nothing worked out. Maybe a recent nightly build of NAnt might fix this issue?

I'm using NAnt 0.85 RC3.

Thank you,

--
Adrian Lazea

Windows Developer
QA Team Lead
Schlund + Partner AG
<http://www.schlund.de>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NAnt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to