Thanks again for your response and patience. I see what you are saying - and therefore copy has the same issue. That is to say if you pass a list of files to copy and an exception is thrown copying one of the files - then the task will not attempt to copy the rest of the files in the list.
failonerror has no impact on this - all it does is prevent the build from failing. Perhaps what it needed is an additional attribute that controls whether or not the Copy/Move tasks suspend the processing remaining files when an error occurs. If this is appropriate - how would one go about requesting / implementing this additional functionality. Gary > > Move is a subclass of Copy. Move has no execute > method of its own; it inherits that of Copy. Copy > checks failonerror within its execute method, so Move > treats failonerror exactly as does Copy. > > -Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
