This article describes how to upgrade from IDC Service Station to Nexus Service Station 1.0.
- You must have administrator privileges.
- There are new Canon cameras supported, meaning the service station is no longer restricted to Canon 1200D or older.
- Microsoft .NET Framework 4.6.2 (bundled with the installer, requires internet access to download)
- If there are custom views, these will need to be installed separately after the upgrade, so make sure they are available.
- Make sure that the current installed Nexus Service Station is not installed under the same folder path as the new version will use:
…\Program Files (x86)\Nexus\Nexus Service Station\
If the current version is installed in the same folder, back it up by changing the name of the containing folder to something else. This is important in order to back up existing data.
The installation of Nexus Service Station software is handled by the Nexus Service Station Installer.exe, distributed by Nexus.
- Double click on the .exe file or run Nexus Service Station Installer.exe from the command line.
Click Install and log on with administrator privileges if necessary.
Nexus Service Station requires a license to run. For more information, see Licensing for Nexus Service Station.
- Once the setup is complete, click Finish to close the installer.
- The software is installed in the folder …\Program Files (x86)\Nexus\Nexus Service Station\ along with its dependencies.
- The shortcut Nexus Service Station, used to start the Nexus Service Station application, is installed under Windows Start Menu.
The installer will never overwrite the following files in an existing installation:
- The main configuration file for the application
- The license file
- All user style and text content files
Due to this being a special upgrade it is necessary to manually configure the customization from the configuration file, style file and locale files. Since all these files are installed in sub folders to the Program Files folder in Windows it will be necessary to use administrator access when editing, renaming and moving files.
SiteKiosk is a lockdown software that allows pre-configured applications to run while blocking access to the OS and other applications installed on the machine. It can be downloaded from www.provisio.com and installed using a self-explaining wizard. See Install software for Nexus Service Station, click Installation procedure, SiteKiosk software.
Since there has been changes to the configuration file it is important to follow these instructions:
- Do not overwrite the new .config file with the pre-existing one. Instead, the customer specific information will need to be manually copied back from the pre-existing configuration file into the new one.
- Take extra care with class and assembly names not to overwrite the new ones with old values from the pre-existing files.
- View Flows have changed to App Flows. This means for each existing view it will be necessary to specify the attribute Type=”view” followed by Class=”<case_sensitive_class_name>” where it previously only said View=”<case_sensitive_class_name>”.
- Under the installation folder there will be a folder called “Sample Configurations”, it contains a few example config files to take inspiration from.
- Do not overwrite the new Style.xaml with the pre-existing one, instead rename the pre-existing Style.xaml to Style.User.xaml and move it into the new installation folder.
- In order to take advantage of the new styles and not end up with a strange interface, or application crashes, it is necessary to clean up Style.User.xaml so that it only contains the styles that are truly custom to this installation.
Regarding user style files:
- You can only have one user style file
- The user style file should only contain customized styles and not be a full copy of the original, the application will fall back to the original for the missing styles
- The user style file is added by the installer if it does not exist, but never overwritten
- The user style file will be deleted by the installer when uninstalling the application
- If you wish to reset completely to the default style simply delete everything between the tags
</ResourceDictionary>in the user style file
- Do not make any modifications to Style.xaml as it will be overwritten with each upgrade from now on.
- Do not overwrite the new locale XAML files with the pre-existing ones, instead rename the pre-existing files to Locale.xx-XX.User.xaml (where “xx-XX” is the name of the locale folder) and move them into their respective locale folder.
- In order to take advantage of the new locale and not end up with a strange interface, or application crashes, it is necessary to clean up the new User locale files so that they only contain the locales that are truly custom to this application.
Regarding user text content files:
- You can only have one user text content file per original locale file
- The text content files should only contain customized text content and not be a full copy of the original, the application will fall back to the original for the missing text content
- All user text content files are added by the installer if they do not exist, but never overwritten
- All user text content files will be deleted by the installer when uninstalling the application
- If you wish to reset completely to the default text content simply delete everything between the tags
</ResourceDictionary>in the user text content file
- Do not make any modifications to Locale.xx-XX.xaml (where “xx-XX” is the name of the locale folder) as they will be overwritten with each upgrade from now on.