Features

• Improvements:
  • SmartAssembly console output is now reported in real-time, instead of at the end of the build, when using SmartAssembly MSBuild Tasks.

Fixes

• SA-2360: Fixed an issue where the 4th part of Windows version was reported as "0" for applications targeting .NET Core, when Automated Error Reporting or Feature Usage Reporting was used.
• SA-2390: Fixed an issue where using method returning value type by reference (e.g. ref int) would cause AccessViolationException in method executing it.
• SA-2408: SmartAssembly command line no longer throws an exception when building a .saproj project with non-existing main assembly path set, when a correct path is passed using the /input parameter.

Features

• Improvements:
  • Enums will be automatically excluded from obfuscation when used by Enum.TryParse method. Previously, Enums were only excluded when Format, GetName, GetNames, Parse, or ToString was called.
  • Nested enums automatically excluded from obfuscation will no longer exclude their parent types from obfuscation.
  • Error message shown during the processing of multi-module assemblies was improved.

Features

• SmartAssembly custom attributes are now available as a NuGet package, RedGate.SmartAssembly.Attributes.
• Added /log, /logLevel, /logFile command line options to ease up logs configuration.

Fixes

• SA-2348: Building Microsoft .NET Standard and Microsoft .NET Core libraries without a .deps.json file is now possible.
• SA-2358: SmartAssembly no longer adds unnecessary references to processed Microsoft .NET Standard 2.0 and Microsoft .NET Core 2.0-2.2 assemblies.
• SA-2369: SmartAssembly SDK no longer throws an exception when calling Database.ExecuteReader() after Helpers.DecodeStackTrace() has been called.
• SA-2372: Dependency search order for Microsoft .NET Framework was changed.
• SA-2340: SmartAssembly.SDK assembly and SmartAssembly.Database sample project now target Microsoft .NET Framework 4.0.

Breaking changes

• In this release of SmartAssembly Redgate Software have renamed the following options to avoid using discriminatory language and better describe their usage:
  • Command-line argument /dbMasterConn was renamed to /dbCreatorConn. If you rely on this command-line argument when executing SmartAssembly, you will need to adjust places where it's used to reflect those changes.
  • SmartAssembly.settings property MasterConnectionString was renamed to DbCreatorConnectionString. If your settings file contains this property, SmartAssembly will attempt to update the configuration file automatically upon startup.