SmartAssembly 7.2.1 and earlier
Published 20 December 2019
SmartAssembly 7.2.2 and later changed the way logging is configured. If you're using newer versions, please refer to Log file for SmartAssembly.
SmartAssembly 6.5 and later contains logging. The log file can be very useful to us if you encounter any problems.
By default, creation of a log file is enabled.
When enabled, the log file is saved in %LocalAppData%\Red Gate\SmartAssembly 7\SmartAssembly.log.
Log file is overwritten each time SmartAssembly is opened. If you want to send us the log file, you copy it before opening a new instance of SmartAssembly.
Enabling logging
To enable logging:
- Using a text editor, open %ProgramFiles%\Red Gate\SmartAssembly 7\SmartAssembly.exe.config
- Uncomment the
<appender>and<root>elements, which are children of the<log4net>element. - Restart SmartAssembly.
A log file is created the next time SmartAssembly is used to process an assembly.
Configuring logging
- To configure where the log file is stored, change the value attribute of the <file> element:
<file value="${LOCALAPPDATA}\Red Gate\SmartAssembly 7\SmartAssembly.log" /> - To configure the logging level used, change the value attribute of the <level> element:
<level value="TRACE"/>
The following levels are valid:
ERROR | Exceptions thrown by SmartAssembly |
WARN | Exceptions and steps taken by SmartAssembly that you may want to be aware of. For example, details of when a type had to be renamed during merging, because the name was already used in the assembly you were merging into. |
INFO | As WARN, and other processing information shown in the user interface. Also lists the assemblies being embedded and merged. |
DEBUG | As INFO, and other information such as where assemblies were resolved, feature usage IDs and XAML references that had to be updated. |
TRACE | Includes all of the above, and details of why classes were excluded from obfuscation or pruning. Note that, when SmartAssembly is used with a large assembly, a log created at this level could be very big. |
