There are a couple of directories that are important to know when you want to change a configuration or if you’re troubleshooting a problem. This quick post will help you get started.
VisitorLink stores its program files, configurations and logs in the application directory. For VisitorLink this is usually found in one these two places:
- 64-Bit Windows: C:\Program Files (x86)\VisitorLink\
- 32-Bit Windows: C:\Program Files\VisitorLink\
If you aren’t sure which version of Windows is installed on your VisitorLink unit it’s probably the 64-bit version. The easiest way to tell is to open Windows Explorer and check if you have a Program Files (x86) folder, if you do VisitorLink should be in it, if you don’t VisitorLink is probably in Program Files.
Configurations directory is where you’ll find your configuration (or configurations if you have more than one). When you start VisitorLink and you’re asked to Select Configuration to Run each configuration is represented by the folder in the
Configurations directory with the corasponding name.
Inside of the Configuration folder you’ll find the Configuration.xml file that contains all of the markup for defining what elements are in your configuration as well as the over all workflow. This file includes the your Lync Provider credentials, all of the screens, buttons, navigation and actions.
The Assets folder is where you’ll find all of the images that are included in your configuration. You can add new images, replace existing ones or remove unused images. There may also be other supporting files including custom DLLs, plugins and whitelist/blacklist spreadsheets.
Layouts is the directory where you’ll find all of the presentational XAML files that you can modify to change the look and feel of your VisitorLink configuration. The Theme.xaml file controls configuration-wide styling as well as the layout for some interface type components. In addition there is a layout template file for each type of screen you have in your configuration named [ScreenType].Layout.xaml that defines the overall layout of that type of screen. Each screen type must have a layout file.
Returning back to the root of the VisitorLink application directory you’ll find a Logs folder; this is where VisitorLink saves daily application logs as plaintext files. These logs can provide valuable information about how VisitorLink is running and what errors VisitorLink has run in to. Along with the configuration this is one of the folders that’s very helpful to zip and send to VisitorLink support if you need to contact us because of a problem.