I'm putting together a system to use NANT and VSS to build and test a web application. All the development is done on my system using VS.NET 2003, and all testing is done on a staging server. The staging server gets the latest pages/code from VSS (using solution task). However, the solution file keeps getting messed up.
On my development machine, the solution file updates itself to refer to the Web Application as being on http://localhost/app.csproj. This works on the dev system, but on the staging server, the project is not located on localhost, as there are a number of websites on that system. As a result, the solution file is incorrect, and the build doesn't work. I've manually edited the solution file so that the web project is a relative path to the solution file, which works fine, but almost everything I do in VS.NET results in the path being made absolute, to localhost, again. I'm not sure if it's a VSS issue, or a VS.NET issue, but I strongly suspect the latter. Is there any way to force VS.NET to use file share access for projects? Or is there some other solution to this problem. Thanks, Erick ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
