Can I override DropLocation target to avoid network latency?
- by Chad
In Team Build 2008, the Drop Location for a build is no longer specified in the .proj file, and instead is stored in the database and maintained in the GUI tool.
The GUI tool only accepts a network path as a drop location (i.e. \\server\share) and will not accept a local path.
Our build server also hosts the dropped files, so it seems that forcing a file copy operation to go through the network share introduces a lot of lag time when copying a large number of files. I would like to override this feature so that I can specify a local directory for drop location, but I can't figure out how.