Re: [nant-dev] NAnt tests, the csproj files and the sln files in CVS

[Scott Hernandez]

Brian,   The VS.Net files are just there for editing (and debugging). I try to keep them in sync with the build files, but they are not there to build the project.   The nightly builds run from the "nightly.build" file via Draco.Net from a new anon cvs checkout. It basically runs a full release build, tests, docs and zips everything up. If people are interested I can have the nightly builds send email to the cvs-commit list so everyone can see it. Or we can even setup a new list just for this purpose, but that seems overkill.   Feel free to submit patches. The tests were not compiled because of NUnit diffs from the past(and the fact that you can not ref a exe--not an issue anymore). I think that VS.Net should be able to build things in a very similar manner to the main buildfile. But I never felt that it had to as it will never be the "correct" way to build NAnt.   Note: See the build file because some of the tests are not compiled/used.   HTH, Scott ----- Original Message ----- From: Brian Deacon To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 9:24 AM Subject: [nant-dev] NAnt tests, the csproj files and the sln files in CVS Recently got yet-another fresh checkout from CVS and ran into a few problems� which then raises a few questions�   The root .build file successfully compiles everything, but the unit tests don�t make it.  Now that I�m typing this, that behavior strikes me as even stranger, because when building from the .sln file, the tests project won�t compile not just because of munged references settings to nunit and nant.core, but some of the tests reference a non-existent default constructor for Project.  (getTask.Project = new Project();)   So my questions: 1)       Am I fat-fingering something, or is the .build file not currently capable of firing off successfully? 2)       Ditto for the .sln file. 3)       What is, or is there, a philosophy regarding the build and sln file?  I�ve noticed they seem to float �near- each other in terms of how and what they build, but not usually identically.  I assume the .build file is the �official� version, as that is what Draco.Net is using, yes?  Wouldn�t it be a Good Thing to keep the sln and .build functionally identical? 4)       Anyone I should ping or any gotchas I should know before I just start submitting patches on this?     TTFN, Brian   (and Ian, I thought you were gonna commit my �vast improvement� on the echo task?) J