I think I've figured out why it isn't working, but not how to solve it. The projects that have a mix of copylocal=true and copylocal=false for references. If I close VS.NET and clean the output bin folder, the solution builds cleanly. If I don't, I get a file locked problem on the compile of NAnt.Core, which then causes problems everywhere else. I've tried setting all the copy locals to false, but there is still a conflict somewhere.
Is there any particular reason why these are set to copy local? I've never had anything but problems using copylocal=true, and haven't found any advantage to it at all. Erick > -----Original Message----- > From: Erick Thompson > Sent: Tuesday, September 02, 2003 12:08 PM > To: NAnt developers (E-mail) > Subject: [nant-dev] Latest build not working? > > > I downloaded the August 31th build from > nant.sourceforce.net/builds, and > opened the sln file in VS.NET 2003. Everything opens correctly, but it > doesn't seem to be building correctly. I'm getting a whole slew of > missing reference errors, missing file errors, and a locking error. > Should I be able to compile NAnt in VS.NET 2003 right out the zip? > > Thanks, > Erick > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
