Hello Eric, You should not have to tweak the project properties in VS.NET.
However, it may be needed to manually copy external dependencies to the build directory before calling the slingshot-generated build file. Best regards, Bernard -----Original Message----- From: Eric Fetzer [mailto:[EMAIL PROTECTED] Sent: Fri 7/11/2003 23:38 To: [EMAIL PROTECTED] Cc: Subject: [Nant-users] Slingshot includes problems I've run into some problems with slingshot building my includes with the incorrect path. I'm guessing that I must be missing something in the Visual Studio .NET as I am extremely new to it. In order to have the paths match between VS and NAnt, I have been going into the Properties of each project (subproject of a solution) and setting the build configuration to Debug\ for Debug and Release\ for Release. I confirm that the build works in VS, save down the .sln file, and then build my .build file based on the .sln file. When I have slingshot create the build file, he is completely getting the reference includes paths wrong so that I have to go in manually and fix them. Note that it is very consistent from project to project what he's confusing. The only thing I can figure is that he is getting confused by the SourceSafe bindings because our projects aren't organiz(s)ed the same way in VSS as our development environment. Can anyone help out here? Thanks - Eric ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
