Candice,
The upgrade notification said there were details as to what was included in the upgrade (ie 7.9) on your blog.
I can't find them there or, as I said before, am I blind?
Am I to assume that IA are not going to post the information on their blog - or anywhere else other than buried in the Help file that you get after you install the upgrade?
Just a simple answer is all that was required. Like - Yes, we're a bit behind and it should be posted in a day or two. Or perhaps, Sorry, it was supposed to be on our Support site's Knowledgebase but we goofed. Or even, it is not our policy to give out detailed information as to bug fixes.
Is no one from IA going to answer GlenG's question:
Is the help file available anywhere other than AFTER installing Installaware? A download link somewhere that I may have missed?
It sort of defeats the purpose when a company is trying to decide whether to update their machines if they can't find out what is in the update until after it's installed.
I'm moving on Candice - It seems I'm not getting anywhere with my questions. I'll just stick to emailing support everytime I want to know something - I usually get a good response and help from them.
For anyone that's interested, this is a cut and past as to what is in the Help file that came with 7.9. I presume you can download the installation file and could have got the chm that way. If there is any more information regarding the upgrade then you'll have to find it yourself:
InstallAware 7 Release 2 contains the following new features and enhancements for developing Windows Installer setups.
IDE
The IDE now substitutes pre-defined system folders with standard MSIcode variables when importing registry entries from COM objects or .REG files. You will still need to make sure that the MSIcode variables substituted by the IDE have been defined by your setup (in case they have not been previously defined).
The IDE now lets you connect directly to the InstallAware Community Center to download new application runtimes or new plug-ins which have been authored by InstallAware or third parties.
The Files and Registry design views now support recursive delete operations on the files, folders, and registry keys being installed.
The Shortcuts, Assemblies, File Associations, ODBC, Services, Environment Variables, Access Control, Drivers, IIS Sites, Shared Folders, SQL Databases, and Scheduled Tasks design views now allow creating and filtering design view elements by setup features.
The Assemblies design view now allows generating native images, registering assemblies for COM Interop, and invoking .NET installer classes on listed assemblies through conveniently located check-boxes.
Tools and Libraries
The underlying technology for connecting to SQL servers such as Oracle, MySQL, and Microsoft SQL Server has been updated.
The built-in update script has been updated to correctly remove previously downloaded update information upon application uninstallation.
The DIFx Driver Install plug-in now performs driver installations using Driver Installation Frameworks 2.1.
Setup Engine
The setup compiler features four new optimization switches for shortening setup build times and improving Windows Installer runtime performance. These switches are also accessible from the command line build tool.
The setup engine has now been optimized to scale for very large setups and provides an approximate 80%-90% runtime performance enhancement for projects involving a lot of MSIcode commands and variables.
The setup engine now waits until the Windows Installer service is available, instead of aborting installation with an error message, when another Windows Installer based setup is in progress. The wait can be cancelled by the end-user if so desired.
The setup engine now compresses its installer cache folder on NTFS volumes, saving disk space, as controlled by the new pre-defined variable $MYAH_COMPRESS_INSTALLER_CACHE$.
The setup engine can now disable Windows Installer rollback to improve runtime setup performance, as controlled by the new pre-defined variable $MYAH_DISABLE_ROLLBACK$.
The setup engine can now disable Windows Vista's Restart Manager to improve runtime setup performance, as controlled by the new pre-defined variable $MYAH_DISABLE_VISTA_RESTART_MANAGER$.
The setup engine no longer aborts on missing variables (such as persistent variables which cannot be reloaded because of a missing installer cache) - instead, such variables are re-initialized on the fly with an empty initial value.
The setup engine now connect to remote IIS metabases, as controlled by the new pre-defined variable $IISHOST$.
The setup engine can now use a custom installer cache location, as controlled by the new pre-defined variable $OVERRIDECACHE$.
The setup engine can now natively work with IIS 7 web servers without requiring the IIS 6 compatibility interface. However, remote IIS functionality is only available in IIS 6 mode.
Setup User Interface
When their Writes Values to Variable Object Behavior is empty, Memo and RichEdit controls now indicate if they have been scrolled all the way to the end by setting their MaxLength property to 2147483647 (the default value for this property is 0). This feature may be used when you need to build dialog boxes for your license agreement (and readme) files, and you require the end-user to read all of the information in the dialog (possibly in addition to checking an "I Agree" box) before moving to the next dialog.
The Panel dialog control now properly resolves variables used within its Caption property.
Updated Scripting Commands
The Generate Native Images command now sets its startup folder to the same folder as the assembly being imaged. It also offers a flag to delete previously generated native images.
The Register Assembly command now sets its startup folder to the same folder as the assemby being registered. It also offers a flag to unregister an assembly.
The Register Library command now sets its startup folder to the same folder as the library being registered.
The Run Program command now sets its startup folder to the same folder as the application being run. A custom startup folder may be specified using the Run Program As command.
The Run .NET Installer Class command now sets its startup folder to the same folder as the installer class being run.