Hi again, did anyone had issues with current path (ie the place where you are when a task is finished) in their script after a recent upgrade of nant ?
I did not investigate much already as I don't have time for this now (I used a simple workaround), but after upgrading nant (previous release was 5 month old) a user script function I called from my build script is lost. The function assumes that we're in the directory where the nant script was started, and rely on this for relative paths resolution. This was working with the previous release I used, but now I'm located somewhere else (probably in a folder where a previous task stopped). I'm not trying to understand fully what's happening today, but I'm interested in any pointer or similar issue, as there is definitely a change in behaviour here. cheers Thibaut nb : I know the best way to lock this issue would probably be to access the nant properties from inside my function to get the base directory, but are we supposed to do it this way ? ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
