I have a build that includes many nested build files. Basically its a directory structure where each level has an understanding of only the folders within it. The master will call the builds in its subfolders, etc. until it finally gets to the build that works on the SLN files from Visual Studio. All is well in every project except I get a sharing violation in one of the build projects. In this case it only happens when the build file in question is called from another build file. If I run it by itself it works great. If I run the SLN file by itself it works great. But if the parent calls into the child which calls the SLN I will get the sharing violation. I imagine this wont be solved without some sample and understanding of whats going on but I just wanted to initally ping the audience and see if anyone has run into this because I couldnt find any solutions elsewhere online.
Brad Eck SitesDynamic (http://www.sitesdynamic.com) Baskets Etcetera (http://www.basketsetcetera.com) ________________________________________________________________ Sent via the WebMail system at sitesdynamic.com ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
