Release v1.14.0.0

The key feature of tis release is "Dynamic Localization" Thank you @Xaddan for preparing an excellent POC for this feature.

It is now enough to specify multiple languages for the project and call the corresponding build method and WixSharp will do the rest. The required transforms will be automatically generated and embedded in the multi-language msi file, which will automatically switch UI to the language of the OS it is being executed on.

var product =
    new ManagedProject("My Product",
        new Dir(@"%ProgramFiles%\My Company\My Product",
            new File("readme.txt")));

product.Language = "en-US,de-DE,ru-RU";
product.GUID = new Guid("6f330b47-2577-43ad-9095-1861bb258777");

product.OutFileName = $"{product.Name}.ml.v{product.Version}";
product.BuildMultilanguageMsi();

Depending on the adoption of this new feature in the future releases BuildMultilanguageMsi may be automatically invoked if the project is identified as a multi-language setup.

The wiki documentation on Localization is yet to be done.

---

• Issue #765: Dynamic localization
• Added WiXUtil ProductSearch element. Used in the same way as the RegistrySearch. The product search is used to determine installation state of other products based on ProductCode or UpgradeCode by Burn bootstrappers.
• Add support for ShortcutProperties (Refs: #218). ShortcutProperty is a simple child element on Shortcuts which has a key and a value. A simple dictionary object has been added to the Shortcut base class and processed later during compilation to emit child XML on the parent Shortcut.
• Issue #774: Using CommonAppDataFolder in project.AddRegValue(RegValue) generates wrong XML
• Issue #748: error for FirewallException. Added localization sample
• Issue #772: Extensions.DeleteIfExists does not delete folders
• Issue #771: default REINSTALLMODE
• Improved auto-assignment of Compiler.ClientAssembly