Difference between revisions of "Release Process"
(→Using Dotfuscator CLI) |
(→Using Dotfuscator CLI) |
||
| Line 1: | Line 1: | ||
== Using Dotfuscator CLI == | == Using Dotfuscator CLI == | ||
| − | Dotfuscator can be executed with command: | + | Dotfuscator can be executed through batch file with command: |
dotfuscator [options] [config_file] | dotfuscator [options] [config_file] | ||
Options may begin with the '/' or the '-' characters. | Options may begin with the '/' or the '-' characters. | ||
| + | |||
| + | The following is a summary of the basic command line options. | ||
| + | |||
| + | /i Investigate only - tells Dotfuscator to not create any output assemblies files. If the configuration file specifies a map file, the results of the run will be found there (this option is close to worthless without generating a map). | ||
| + | |||
| + | /v Verbose output - induces Dotfuscator to provide information about its progress during execution. The level of detail here will likely change between releases. | ||
| + | |||
| + | /q Quiet output - tells Dotfuscator to run completely without printed output. This is suitable for inclusion into application build sequences. This option overrides verbose mode. | ||
| + | |||
| + | /? Print help | ||
| + | |||
| + | [config_file] Configuration file containing runtime options. | ||
| + | |||
| + | The configfile is a configuration file that is required for every run of Dotfuscator. Notice you do not enter configuration information or target assemblies on the command line. This information must be found in the configuration file. | ||
| + | |||
| + | Extended options are designed to allow for basic obfuscation from the command line, without requiring you to first create a configuration file. If you use a configuration file with an extended command line option, the command line option supplements or overrides the commands in the configuration file. See [https://www.preemptive.com/images/stories/Dotfuscator/Supplementing_or_Overriding_a_Configuration_File_from_the_Command_Line.html Supplementing or Overriding a Configuration File from the Command Line] for more information. | ||
| + | |||
| + | === Configuration File === | ||
== Using InstallAware CLI == | == Using InstallAware CLI == | ||
Revision as of 08:21, 29 December 2016
Using Dotfuscator CLI
Dotfuscator can be executed through batch file with command:
dotfuscator [options] [config_file]
Options may begin with the '/' or the '-' characters.
The following is a summary of the basic command line options.
/i Investigate only - tells Dotfuscator to not create any output assemblies files. If the configuration file specifies a map file, the results of the run will be found there (this option is close to worthless without generating a map).
/v Verbose output - induces Dotfuscator to provide information about its progress during execution. The level of detail here will likely change between releases.
/q Quiet output - tells Dotfuscator to run completely without printed output. This is suitable for inclusion into application build sequences. This option overrides verbose mode.
/? Print help
[config_file] Configuration file containing runtime options.
The configfile is a configuration file that is required for every run of Dotfuscator. Notice you do not enter configuration information or target assemblies on the command line. This information must be found in the configuration file.
Extended options are designed to allow for basic obfuscation from the command line, without requiring you to first create a configuration file. If you use a configuration file with an extended command line option, the command line option supplements or overrides the commands in the configuration file. See Supplementing or Overriding a Configuration File from the Command Line for more information.
