In cases where the full path to your source is not the same on both machines, you also need to set up a mapping that tells Wing where it can find your source files on each machine.
This is done with the Location Map preference, which lists corresponding local and remote directory locations for each remote host's dotted quad IP address.
Each host IP address in the location map is paired with one or more (remote_prefix, local_prefix) tuples. The remote file prefix will be a full path on the debug server's file system. The local file prefix is usually the full path of a local directory, though it may also be a file: url.
The best way to understand this is to look at the Location Map Examples.
When running Wing IDE on Windows XP, UNC formatted file names such as \\machine\path\to\file may be used. On other Windows systems, you must map remote drives to a drive letter such as F:. In cases where setting up a persistent drive mapping is a problem, use a cmd.exe script with a net use command to map the drive on demand.
Note that making symbolic links on the client or server will not work as an alternative to using this mapping. This is a side-effect of functionality in the debugger that ensures that debugging works right when symbolic links are present: Internally, source file names are always resolved to their actual full path location.
|« 13.1. Remote Debugging||Table of Contents||18.104.22.168. File Location Map Examples »|
22.214.171.124. File Location Map Examples