Re: [nant-dev] property overwrite attrib

2005-01-26 Thread Gary Feldman
>From: "Jamie Briant" <[EMAIL PROTECTED]> >Sent: Wednesday, January 26, 2005 12:49 AM > The first is dangerous because when a programmer decides to change some > build.config's to build.local.config (for example) they are guaranteed > at some point to miss one. Not every time. Not even very often

Re: [nant-dev] property overwrite attrib

2005-01-26 Thread Gert Driesen
Hi Jamie, We listen to our "customers", so we've decided to no longer mark that attribute as deprecated. Gert - Original Message - From: "Jamie Briant" <[EMAIL PROTECTED]> To: Sent: Tuesday, January 25, 2005 2:56 AM Subject: [nant-dev] property overwrite attrib Does this not seem out

RE: [nant-dev] property overwrite attrib

2005-01-25 Thread Jamie Briant
sing, may I suggest a new option be put in its place that has the same effect, such as "overwriteexisting", or "lookmeupinthemanual". Jamie -Original Message- From: Troy Laurin [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 9:33 PM To: Jamie Briant Cc: nant-

Re: [nant-dev] property overwrite attrib

2005-01-25 Thread Troy Laurin
Jamie Briant wrote: Does this not seem outstandingly dangerous to anyone? Its just asking for errors where only one of the “build.config”’s is changed. Is there a good reason that the following is deprecated? James, I'm not sure why the first would be dangerous but the second