Tim Mayert wrote:
the solution exists before building all the projects then my validation step will give me a false positive, meaning that it will show the correct files that failed to build, but some of the files are listed because they were to be created, but the solution exited before those projects could be built....
I don't understand. If it's showing the correct files, why is it a false positive? The validation step shouldn't care why they weren't built, just that they weren't.
So if anyone knows of a way to make NAnt continue building the current solution file, even after some projects failed to build, then I would really appreciate hearing from you!!!!
I suggest splitting the solution into independent solutions, or possibly using build configurations to achieve the same effect. I don't know if there's currently a way to force NAnt to continue, though it's surely possible in theory. The problem, however, is that there's a presumption that at least some projects later in the build depend upon projects built earlier in the build. If an earlier project fails, then the later projects will also fail (or worse, be built against an old version, which can happen if older .dlls are still lying around for some reason). If, in fact, you have later projects with no dependencies on earlier ones, then there's nothing stopping you from putting them into separate solutions, other than the labor involved. Alternatively, depending on what your projects are like, you might want to invoke the compilers directly from NAnt, e.g. using the <csc> or <vb> tasks instead of the solution task. There are tradeoffs both ways; I wouldn't go down this route unless you can be sure that you can accurately describe the things to compile using a fileset, as well as being sure you can correctly manage the compile options separately from the project files.
How do others handle this issue? Is there another way to handle the solution files so as to build the entire solution?
The situation in which this occurs for us is for the test projects, which will frequently fail if not updated or checked in. Hence we have one master solution that builds the product, but not the tests, and then project-specific solution files for each of the tests. That way, a failure to compile a test won't prevent other tests from running or the rest of the product from building. Gary ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
