WebChangeMonitor comes with options that can be set at the command line and will override what's in the config (INI) file. Command line options have a short and a long version. Further command line options maybe added later, so first of all to get a list of all command line option, please run:
WebChangeMonitor.exe /?
At the time this article was written (targeting release 20.06), there are the following options available:
- /H or /? (--help) = Command line help
- /t (--translate) = Translate application into a locale that is supported and implemented. If your language is missing you can contribute!
- /m (--multi) = Allow multiple instances of the application. (By default, only a single instance of WCM is allowed to avoid data corruption if no setup properly.)
- /l (--logfile="...") = Setup a dedicated Log-File to use. If the file cannot be accessed/opened the application will fall-back to the default log file.
- /s (--statedb="...") = Setup a dedicated State DataBase File to use. If the file cannot be accessed/opened the application will fall-back to the default state database file.
- /o (--htmlfile="...") = Setup a dedicated HTML-(Log-)File to use. If the file cannot be accessed/opened the application will fall-back to the default HTML (log) file.
- /c (--cfgfile="...") = Setup a dedicated Config-File to use. If the file cannot be accessed/opened the application will fall-back to the default config file.
- /p (--tempdir="...") = Setup a dedicated folder for Temporary Files to use. If the folder cannot be accessed/opened the application will fall-back to the default folder.
As an example: WebChangeMonitor.exe /m --logfile="C:\Fldr\Log.txt" --cfgfile="C:\Fldr\MyCfg.ini"
Further options can be added on request. If you need another option, please file a feature request.
Last edit: Morten MacFly 2021-05-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WebChangeMonitor comes with options that can be set at the command line and will override what's in the config (INI) file. Command line options have a short and a long version. Further command line options maybe added later, so first of all to get a list of all command line option, please run:
At the time this article was written (targeting release 20.06), there are the following options available:
- /H or /? (--help) = Command line help
- /t (--translate) = Translate application into a locale that is supported and implemented. If your language is missing you can contribute!
- /m (--multi) = Allow multiple instances of the application. (By default, only a single instance of WCM is allowed to avoid data corruption if no setup properly.)
- /l (--logfile="...") = Setup a dedicated Log-File to use. If the file cannot be accessed/opened the application will fall-back to the default log file.
- /s (--statedb="...") = Setup a dedicated State DataBase File to use. If the file cannot be accessed/opened the application will fall-back to the default state database file.
- /o (--htmlfile="...") = Setup a dedicated HTML-(Log-)File to use. If the file cannot be accessed/opened the application will fall-back to the default HTML (log) file.
- /c (--cfgfile="...") = Setup a dedicated Config-File to use. If the file cannot be accessed/opened the application will fall-back to the default config file.
- /p (--tempdir="...") = Setup a dedicated folder for Temporary Files to use. If the folder cannot be accessed/opened the application will fall-back to the default folder.
As an example:
WebChangeMonitor.exe /m --logfile="C:\Fldr\Log.txt" --cfgfile="C:\Fldr\MyCfg.ini"Further options can be added on request. If you need another option, please file a feature request.
Last edit: Morten MacFly 2021-05-27