SmartAssembly
Latest version: 6.7
Log file for SmartAssembly
Date: 10/20/2011
Product: SmartAssembly
SmartAssembly 6.5 and later contain logging. The log file can be very useful to us if you encounter problems.
By default, creation of a log file is disabled.
When enabled, the log file is saved in %LocalAppData%\Red Gate\SmartAssembly 6\SmartAssembly.log
Enabling logging
To enable logging:
- Using a text editor, open %ProgramFiles%\Red Gate\SmartAssembly 6\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 6\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. |
Was this article helpful?
SmartAssembly
- Using Smartassembly to obfuscate a windows service
- Obfuscation not renaming identically-named methods in different classes
- Serialization exceptions occurring in obfuscated assemblies
- SmartAssembly skipping obfuscation of some classes in your assembly
- SmartAssembly is not merging or embedding all assembly dependencies
- Can I customize the path to the MDB database?
- System.InvalidOperationException when attempting to connect to local SmartAssembly database
- Protecting website code using SmartAssembly
- Visual Studio Deployment Projects including unprotected builds
- SmartAssembly MSBUILD tasks failing because of difference in log4net assembly
- SmartAssembly Error Reporting: This application has submitted too many reports
- The assembly is being merged, but the dependent assembly isn't
- ERR 2002: Server did not recognize the value of HTTP Header SOAPAction
- The error report is not associated with a valid project ID - SmartAssembly
- Application built with an evaluation edition of SmartAssembly
- How end users can change their participation in Feature Usage Reporting
- Log file for SmartAssembly
- Moving SmartAssembly to another computer
- 'Using JET databases is not possible in 64-bit applications' error when using MSBuild or TFS
- SmartAssembly stack trace is invalid when Method Parent Obfuscation is enabled
- Upgrading SmartAssembly version 4.x to version 5
- Upgrading SmartAssembly Standard to Professional
- Problems building WPF applications with SmartAssembly 6.7
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SmartAssembly
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SmartAssembly for obfuscation