Maybe this is why (clipped comment from a distantly related thread below) I didn't see this if it's already documented, but it took me a bit of serendipity (just happening to remember wondering why in tarnation the force attribute for <call/> was there to begin with from sleep-deprived reading many nights ago) to figure out how to get all my multiple calls to reused targets to execute properly...
Is force=false by default really the behavior that a user would expect of build management widget?? (I didn't, obviously -- but I'm abnormal. I have a diagnosed refactoring condition. :) It'd be handy to have a global option to set force=true|false for the whole build manifest... especially when I start making heavier use of <include/> for libraries of reusable targets. But maybe there's a simpler way to do what I'm doing, so I've attached the build file in question if anybody's got time to knoodle over it... (Kudos to whoever wrote the <sql/> task - it rawkz! Replacing oodles of batch files and a homegrown wrapper for ISQL is muy kewl. The only little fly in the ointment is that - like copy - it doesn't seem to take a fileset property, either. *pout* But I can work around that with foreach for now.) -----Original Message----- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 5:42 PM To: Yogesh Shetty; [EMAIL PROTECTED] Subject: Re: [nant-dev] NUnit & Config No, it's not. It's an attribute of a build element/type, not a task. For now, only tasks (and their attributes) are documented. Gert
Database.Reload.build
Description: Database.Reload.build
