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

Reply via email to