Brad Wilson wrote: >Ian MacLean wrote: > >>Agreed. The basic issue is that the C# task has no knowledge that the >>build file has been changed. If we make it compare tstamps for the build >>file against the binary that sould give us enough infomation to work >>this out. This would force rebuild for all csc takss in a build file but >>thats better than not rebuilding I guess. I don't think we're handling >>changes to resx files either with regard to buildability. I'll take a >>look at fixing this. >> > >Hmm... when I change my build file and need a rebuild, I just force one by >adding "clean" to my target list (I always keep a "clean" task anyway, so >I'd rather not have a change to the .build file necessitate a clean rebuild, >if it turns out all I was doing was adding comments or changing some other >unrelated task). > I agree. I could imagine a build file having say 30 csc tasks. You don't want all these being rebuilt with every edit to the build file. I don't think that adding an attribute is the right solution either - you'd then get some cscs tasks re-building and otheres not depending on which ones set the attribute. I like the way that you can change one .cs file and only the csc task that uses it will rebuild. using the clean target is a good idea - you just have to remember to do it.
Ian _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
