We also check in our binaries (don't ask). I have found that the best way to ensure that everything gets updated in this scenario is to delete the files after the VSS checkout.
Nick Varacalli -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fetzer Sent: Friday, October 03, 2003 16:13 To: NAnt Developers Subject: [nant-dev] <solution> The last few days, I've run into a very strange situation. I'm doing vsscheckin's on certain dll files with my build because the developers don't want to have to build all the projects constantly (and change is big now - new app). So I have to do a vsscheckout at the beginning of the build process. With one particular project, it builds the project successfully, but for some reason, doesn't replace the .dll. Not only does <solution> not replace it, but VS.Net doesn't either (unless doing rebuild). This would be cool if nothing had changed, but it has and causes later projects to fail. Is there a way to force <solution> to rebuild, or if not, a way to modify solution to do such? Thanks in advance! Eric __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ------------------------------------------------------- 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
