The File Path Substitutions tab allows you to specify how file paths can be modified to account for copying a build from a build machine to a development machine or test machine.

 

File paths need to be modified otherwise the debug information will point to source code in locations that don't exist on the new machine.

 

There are no substitutions set up by default:

 

 

 

File Path Substitutions

 

Some software development schemes have multiple rolling builds of their software, often enabled by using substituted disk drive naming schemes.

 

When you download the build to your development machine for development and testing, debugging information may reference disk drives that don't exist on your machine, for example, drive X: while your machine only has C:, D:, and E: drives.

 

Or you may just be copying a build from a drive on a development machine to a subdirectory on a drive on your test machine.

 

These options let you remap the substitution so that the Performance Validator looks in the correct place for the source code.

 

•Add adds a row to the File Paths Substitutions table enter the new path that will replace the old path in the New Path column click in the Old Path column enter the path that is being replaced

 

For example, you might enter c:\users\stephen\documents for the new path and f:\dev\build for the old path.

 

You can double click to edit drives and paths in the table, or remove items:

 

•Remove removes selected substitutions from the list

 

Alternatively, press to delete selected items, and + to select all items in the list first.

 

 

Example: Changed disk drive

 

Example: Project copied to a new location

 

 

 

Reset All - Resets all global settings, not just those on the current page.

 

 

Reset - Resets the settings on the current page.