View Full Version : [CLOSED] Deploy path cannot be set relative to the project.
7 Nov 2011, 7:40 AM
When deploying a new project, if the Deploy Path has not been set, the user is prompted for a path with the file chooser dialog. If you select a directory to deploy to, the absolute path is saved in the Project Settings. If you open Project Settings to change the Deploy Path, as soon as you click the text field, the file chooser dialog appears. I need to choose a relative path, such as "." as the Deploy Path, so that other developers can also open, edit and deploy, using different absolute paths, but same relative path.
I am using Windows 7, so behavior may be different on other platforms.
8 Nov 2011, 4:03 PM
Allowing for relative paths is a feature we have to remove because it added lots of problems e.g. circular copies
I imagine the xds file should be something like an sln file for Visual Studio. Not something that members of the team check in changes to. Each developer would either have there own export location or the team can standardize with the same drive setup and use c:\inetpub\wwwroot ....
The relative pathing was nice but I fear it's return is very unlikely. Most builders / editors don't allow for this and we now know why.
19 Apr 2012, 4:00 PM
Would it be possible to add a warning about this deployment path limitation? Right now relative paths are accepted and it even appears to deploy without any errors, though the files are not copied. The deployment dialog is very technical and it's not immediately obvious if what you see is a success case, until you've seen the file list appear on a successful deployment...which of course, if you are just getting started, hasn't happened yet.
Powered by vBulletin® Version 4.1.5 Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.