The Summary, UAC, and ISO design view now lets you set the ISO/IEC 19770-2:2009 software identification (SWID) tag for your application.
The New Project dialog now lets you promote any setup project into a project template.
The Replace dialog now replaces all instances of text found in a setup command, instead of replacing only the first instance.
The Authenticode Signature design view now has an option to automatically code sign all .EXE, .DLL, .OCX, .SYS, .CPL, .DRV, and .SCR files being installed by setup for Windows 8 logo program compliance.
The Build Settings design view now has an option to automatically build all setup layouts as MSI files.
The Project Manager now opens all script and dialog browsers inside the active project folder.
The Add Dialogs to Project window now permits adding more than one custom dialog simultaneously.
You may now create and navigate to bookmarks inside the MSIcode script editor.
The code navigation drop-downs now include the full list of available MSIcode script bookmarks.
The IDE now prompts to confirm when you attempt to save a read-only file, to ensure your project folders remain synchronized with source control.
The IDE most recently used file list now accommodates double the number of projects and displays full project paths on mouse-over.
Tools and Libraries
The Dialog Editor now automatically refactors rules when the name of a dialog control is changed.
A Visual Studio 2012 Add-In is now available. The add-in automatically generates and builds InstallAware setups for your Visual Studio 2012 solutions. These may then be built as App-V virtualized packages using the Build App-V Package tool.
All Visual Studio Add-In generated projects have been updated for the Microsoft .NET Framework 4.5 eco-system, automatically including the new Microsoft .NET Framework 4.5 runtimes as necessary.
Group Policy Wizard generated MSI files now do not display dual User Account Control elevation prompts. Elevation prompts are no longer hidden in the background.
Group Policy Wizard generated MSI files now display progress feedback with cancel support when extracting large payloads.
The App-V Viewer tool has been updated with performance and stability improvements.
The command line build tool may now add patch references not included in the original project.
A new MiaBuildProjectEy function is available as part of the automation interface which displays the build window with a parent handle.
A new .NET assembly is now available as part of the automation interface for use within the .NET eco-system.
New MFC, C#, and ASP.NET samples are available for use with the automation interface.
The Product Name and Product Version fields in the version information structures of built EXE files are now populated.
A new .NET Plug-In Bridge is available for calling managed code plug-in assemblies from your setups.
A new runtime is available for Microsoft SQL Server 2012.
The runtimes for Microsoft .NET Framework 2.0, 2.0 with Service Pack 1, and 2.0 with Service Pack 2 have been updated to enable installation on Windows 8 and Windows Server 2012.
New runtimes are available for the Microsoft .NET Framework 4.5 in both 32 bit and 64 bit flavors.
New runtimes are available for the Microsoft Visual C++ 11 Runtime in both 32 bit and 64 bit flavors.
New runtimes are available for the Microsoft SQL Server 2012 Native Client in both 32 bit and 64 bit flavors.
New runtimes are available for the Microsoft IIS Express 8 Web Server in both 32 bit and 64 bit flavors.
The new $CHARSET_OVERRIDE$ pre-defined variable permits to automatically change dialog font character sets without having to duplicate dialogs in multi-lingual setups.
Setup billboards now resume automatically from the last billboard shown instead of resetting to the first billboard between different displays of progress dialogs.
The $NATIVE_LOGGING$ pre-defined variable can no longer be overridden unless a full file path (including full folder information) is provided.
Double-buffering for setup controls is now selectively enabled based on the active system theme, for improved display of setup controls.
The new #SIGN_ALL_INPLACE# pre-defined compiler variable controls whether code signing occurs in-place or out-of-place during a build.
New Scripting Commands
The new Evaluate XPath Query command runs an XPath query against a specified XML file.
The new For Each and Next commands allow for the construction of for loops.
Updated Scripting Commands
The Advertised Shortcut/Create Shortcut commands can now run applications as administrator on operating systems with User Account Control (or run them with alternate credentials on operating systems older than Windows Vista).
The Advertised Shortcut/Create Shortcut commands can now prevent the automatic inclusion of shortcuts on the new Windows 8 Start Screen.
The Advertised Shortcut/Create Shortcut commands can now prevent the user pinning of applications.
The Break and Continue commands allow for immediately terminating or continuing to the next iteration of for loops.
The Get System Settings command now supports Microsoft Hyper-V virtual machine detection.
The Most Recently Used Files listing was half empty.
Unpin from Start Screen was not functioning correctly with the final release of Windows 8.
Set Breakpoint was not displaying the breakpoint after a bookmark had been inserted.
Edit XML File lacked a Browse button to pick the XML document to edit visually.
64 bit ODBC data sources were not created successfully using the Native Engine.
The automation interface lacked a build function which permitted specifying the parent window handle to the build window.
Read-only files were always overwritten when saving projects.
The Impact theme contained a production progress dialog from InstallAware Virtualization, instead of the actual template progress dialog with interactive HTML.
Inserting AVI animations in the Dialog Editor caused seemingly random errors with locating the AVI file.
Multiple files could not be selected to add to a setup project as new dialogs.
The Project Manager did not remember the previous folder and/or the project folder used when last adding resources to a project.
Patch references could not be added via the command line Build Tool.
Single Instance setups, when launching second or more instances, would crash with random errors.
The Native Engine did not properly load old installation data in certain cases.
Patches did not properly load old installation data if the product name was changed between versions.
Run commands in the IDE did not run new direct MSI built setups.
Some duplicate compiler variables were re-injected in duplicates (or more) when a build failed with a compiler variable conditional error.
Batch builds set some build mode compiler variables incorrectly.
Patches built after batch builds may have failed to enable the patch compiler variables, causing problems with actual patch application.
Compiler variable override values sometimes failed to override their desired targets if a default value was previously defined.
Patch references did not accept new direct MSI built setups.
The Group Policy built MSI files lacked payload extraction progress report.
The Group Policy built MSI files could not be aborted once starting extraction.
The Group Policy built MSI files caused double User Account Control elevation prompts.
The Group Policy built MSI files caused User Account Control elevation prompts that were sometimes hidden in the background.
Adding new scripts did not default to the current project folder.
Saving existing scripts did not default to the current project folder.
Automatic code signing for all setup binaries failed after one effort, instead of accounting for intermittent network connectivity issues.
The application user model identifier was sometimes not being properly set on Windows 8.
If Visual Studio 2012 was started at least once before installing InstallAware, the InstallAware Add-In for Visual Studio 2012 would not be registered with Visual Studio.
Very slow runtime performance with InstallAware setups using large scripts.
Incorrectly overriding the NATIVE_LOGGING pre-defined variable without path information caused complete system drive deletion.
Some feature descriptions in the InstallAware setup were not fitting in their allocated space.
Shortcuts could not be pinned into the Start Screen with the final release of Windows 8.
Low resolution icons were incorrectly used in the New Project | Custom tab when promoting setup projects into user made templates.
There was no programmatic method to update the character set of dialog controls.
The documentation for Set Access Control did not make it clear that the command is non-recursive in nature.
The Display Dialog command editor control states malfunctioned in certain cases, leaving certain settings disabled until the command editor was re-initialized with the same command line twice in succession.
ASP.NET version 4 application pools created by the Create Virtual Folder command sometimes contained superfluous versioning information in the application pool name.
ASP.NET version 4 application pools created by the Create Virtual Folder command sometimes were accompanied by an unintended ASP.NET version 2 application pool in the desired name.
Literal file exclusions were not honored by the Install Files command – unless wildcards were used, the exclusions would be still included in setup.
The If command editor control states malfunctioned in certain cases, leaving certain settings disabled until the command editor was re-initialized with the same command line twice in succession.
The GlowLabel control malfunctioned when double buffering states were being intelligently managed,
The .NET Plug-In Bridge did not properly pass the state of variables back to the setup script.
Installing .NET versions 2 through 3.5x failed on Windows 8.
InstallAware built plug-ins did not correctly set their parent window handle to the InstallAware IDE.
The Dialog Editor did not refactor rules when a component name was changed, instead deleting all rules referring to the old component name.
Progress billboards did not resume from the last billboard shown between different displays of HTML progress enabled billboards, all activated within the same setup session.
Search and Replace did not replace all occurrences of a given string literal in a single setup command.
The Set Variable command editor sometimes did not reset the state of the “Persistent” option.
The Continue command did not re-evaluate the loop conditional for While loops, unconditionally skipping to the next loop iteration.
A superfluous PackageAware folder would be created every time the InstallAware IDE or a built setup was run.
When setup invoked system tray commands, and the Explorer shell was unavailable or not started yet, setup would fail with a runtime error.
All list views used in the IDE and setup engine lacked translucent selection rectangles.
The SQL Server 2012 (Denali) runtime installation failed on Windows 8.
Virtual Machine detection failed to detect Hyper-V based virtual machines.
The Portuguese spelling was incorrect in built setups and various places throughout the InstallAware tool chain.
The command line Build Tool had intermittent build failures when running on 64 bit Windows.
The InstallAware IDE instance name was incorrect.
The Convert Path command behavior was undefined when the specified path did not already exist.
Editing a Create Shortcut command in the visual designers sometimes lost the associated icon.
In rare instances, when a lot of identically named files were being included inside a single Web Media Block, the Weblock processing could fail at runtime, resulting in misleading extraction failure errors.
Hybrid installation projects which combined 32 bit and 64 bit driver installations inside the same Web Media Block or the main setup executable would succeed in installing only the last referenced bitness driver in the setup script.
The product name field in built EXE files was not injected.
The product version field in built EXE files was not injected.