Home » Support » Index of All Documentation » Wing IDE Reference Manual » Advanced Debugging Topics » Remote Debugging »

11.1.0. File Location Maps

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.

One of the host IP addresses within this preference can be set to "*" to define a default mapping for all hosts that are not otherwise specified in the location map.

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 should be a URL, optionally starting with file: (this URL should not contain backslashes (\), even if the local host is a Windows machine) or a UNC \\server\share\dir style path name.

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.

Section Contents

11.1.0.0. File Location Map Examples