Release v1.2.0 alpha 3

Highlights of v1.2.0a3

This alpha release includes feature updates and bug fixes. Two callouts are the optimisation flags, and using VisualStudio files to determine an environment to run in (avoiding hardcoded versions).

• Reworked compiler optimisation flags; common settings (Speed/Size) are now more like what you should expect, while Custom is now deferred to the chosen compiler to configure to anything it chooses.
• Windows .rc files that were procedurally generated by BAM are now only written to disk when either a) they don't exist, or b) they've changed since the last write. This was causing unnecessary relinks in VisualStudio executable projects.
• Added better error text when more than 65K objects exists in the temporary folder, and BAM now automatically deletes all of its temporary files.
• Added Bam.Core.ModulePackageDirectoryRedirectAttribute as a per-module option to the per-package existing attribute Bam.Core.PackageDirectoryRedirectAttribute.
• Bam.Core.OSUtilities.GetInstallLocation now looks in standard install locations on Windows, as well as custom locations, and can cache executable paths based on custom keys.
• An overload of Bam.Core.Graph.FindReferencedModule<T>(env) can now be used in patch functions.
• Bam.Core.IOverrideModuleConfiguration.execute() is now aware of the Bam.Core.Environment.
• Added Publisher.ZipModule to archive a directory. (Current use-case is in the Python standard library.)
• BAM now includes the vswhere NuGet package.
• VisualC packages now use vswhere and vcvarsvall.bat to determine an environment to execute tools in.
• Setting C.CModule executable versions has been made easier with a SetSemanticVersion function (and several overloads).

Full changes since v1.2.0a2

Known issues

Bug list