SmartAssembly 6.12 release notes
Published 17 January 2018
October 12th, 2018
This is a minor release of SmartAssembly (6.12.7):
Fixes
SA-2100:Running SmartAssembly as MSBuild task no longer fails.- If you encountered this issue, you might need to kill all instances of
MSBuild.exeprocess after installing this release, for the fix to take effect.
- If you encountered this issue, you might need to kill all instances of
October 1st, 2018
This is a minor release of SmartAssembly (6.12.6):
Fixes
SA-1967:In applications built with default error reporting template "Dialog box + email address collection" behaviour of the "Save As" button was improved.
July 24th, 2018
This is a minor release of SmartAssembly (6.12.5):
This release fixes a critical issue where it was possible to execute code by selecting a source assembly containing a .NET object with an embedded resource file. (CVE-2018-14581)
Thanks to Soroush Dalili from NCC Group for bringing this to our attention.
July 3rd, 2018
This is a minor release of SmartAssembly (6.12.4):
The "I want to reduce unused allocated memory" option was removed.
Fixes
- SA-1747 — Tamper Protection now works for embedded assemblies.
March 8th, 2018
This is a minor release of SmartAssembly (6.12.3):
Fixes
- SA-2046 — Improving error reporting feature for situations when stack is not empty after stepping-in try region.
- SA-2054 — Changed TypeDefinition comparing to match com-imported types.
February 22nd, 2018
This is a minor release of SmartAssembly (6.12.2):
Fixes
- SA-2052 - SmartAssembly failed to process assemblies referenced to mscorlib 5.0.5.0
- SmartAssembly informations changed to be more user-friendly.
January 19th, 2018
This is a minor release of SmartAssembly (6.12.1):
Fixes
- Fixed an issue introduced in the new release on Options screen.
January 17th, 2018
This is a minor release of SmartAssembly which includes the following enhancements and bug fixes:
Features
- SA-1569 — You can now force the obfuscation of members that would normally be excluded by safety mechanisms.
In some circumstances, SmartAssembly would automatically exclude some members from obfuscation, if it predicted it could break the final assembly. With this update, you can (at your own risk) skip all SmartAssembly's safety-checks using [ForceObfuscate] attribute for definitions of: methods, classes, structs, properties and fields. By default, marked members will be renamed in accordance with the chosen Name Mangling setting, although you can use [ForceObfuscate(true)] to rename them in a more predictable way, if need be.
Fixes
- SA-1734 — SmartAssembly failed to process Portable Class Libraries targeting .NET 4.5+.
