Is there more information about this upcoming release?
Is there more to it than just the Hybrid installation technology?
I would like more information before sending and upgrade request to our purchasing department.
InstallAware 10
Re: InstallAware 10
Is there anything in particular you're interested in finding out about?
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
Re: InstallAware 10
The list of new features and bug fixes.
Re: InstallAware 10
InstallAware 10 contains the following new features and enhancements:
IDE
The Find, Find Next, and Find and Replace tools may now perform both case sensitive and case insensitive operations.
Tools and Libraries
A new Native Setup template is available for creating hybrid 32 bit-64 bit application installers using the new native code setup engine, including support for uninstallation of old product versions as well as the modification of setup features during maintenance mode.
A new Win64 Setup template is available for creating 64 bit application installers. The template contains pre-defined system folders for both 32 bit and 64 bit locations.
Plug-Ins
The MS SQL Server plug-in no longer attempts connections to Microsoft SQL Server on port 1433 by default. However, any desired port may be specified.
Setup Engine
A new Native Code Setup Engine is now built-in. The native code setup engine is capable of executing each Windows Installer based action without requiring Windows Installer on the target system. Additionally, the native code setup engine enables setup actions to execute immediately, without deferring them until Apply Install is called - unlike the Windows Installer engine.
The new #NO_MSI# pre-defined compiler variable controls whether MSI databases are created as part of a build process.
The new $NATIVE_ENGINE$ pre-defined variable controls whether the native code setup engine or the Windows Installer engine will be driving the installation.
The new $DELAYUNTIL_APPLYCHANGES$ pre-defined variable permits emulating Windows Installer engine behavior by delaying the immediate execution of setup actions, even when the native code setup engine is active.
The new $NATIVE_ERROR$, $NATIVE_OVERWRITE$, and $NATIVE_OVERWRITE_OLDER$ pre-defined variables control how the native code setup engine handles errors and overwrites during native code installations.
The new $NATIVE_LOGGING$ and $NATIVE_ROLLBACK$ pre-defined variables control whether the native code setup engine permits uninstallations and rollbacks of native install actions.
The new $RECOMMENDEDUPGRADE$ and $NATIVE_OLDLOG$ pre-defined variables indicate if and where an old setup using the native engine was found on the target system.
Setup User Interface
Images may now be loaded onto dialog controls at runtime as follows: Define a script variable that has the same name as the target TImage control on your dialog. Before showing the dialog, set this variable to the full file system path of the image that you wish loaded onto the control (such as a file in $SUPPORTDIR$, or a file installed/already present on the target system). If the variable is not defined in the script or does not contain the full path of a file that exists, the existing image will be used and no new image will be loaded.
New Scripting Commands
The new Break and Continue commands allow for immediately terminating or continuing to the next iteration of repeat and while loops.
The new Reboot and Login command restarts the target system and resumes setup after the Windows shell has been loaded, complementing the Reboot and Resume command which restarts the target system and resumes setup before the Windows shell has been loaded.
The new Repeat and Until commands allow for the construction of repeat loops.
The new While and Wend commands allow for the construction of while loops.
Updated Scripting Commands
The Get System Settings command now supports obtaining the exact resolution of the target system display, as well as obtaining the exact amount of physical RAM installed.
The Install Files, Install Assembly, Install Service, Install ODBC Driver commands now support relative path names and environment variables for source file paths. All paths are relative to the root project folder.
IDE
The Find, Find Next, and Find and Replace tools may now perform both case sensitive and case insensitive operations.
Tools and Libraries
A new Native Setup template is available for creating hybrid 32 bit-64 bit application installers using the new native code setup engine, including support for uninstallation of old product versions as well as the modification of setup features during maintenance mode.
A new Win64 Setup template is available for creating 64 bit application installers. The template contains pre-defined system folders for both 32 bit and 64 bit locations.
Plug-Ins
The MS SQL Server plug-in no longer attempts connections to Microsoft SQL Server on port 1433 by default. However, any desired port may be specified.
Setup Engine
A new Native Code Setup Engine is now built-in. The native code setup engine is capable of executing each Windows Installer based action without requiring Windows Installer on the target system. Additionally, the native code setup engine enables setup actions to execute immediately, without deferring them until Apply Install is called - unlike the Windows Installer engine.
The new #NO_MSI# pre-defined compiler variable controls whether MSI databases are created as part of a build process.
The new $NATIVE_ENGINE$ pre-defined variable controls whether the native code setup engine or the Windows Installer engine will be driving the installation.
The new $DELAYUNTIL_APPLYCHANGES$ pre-defined variable permits emulating Windows Installer engine behavior by delaying the immediate execution of setup actions, even when the native code setup engine is active.
The new $NATIVE_ERROR$, $NATIVE_OVERWRITE$, and $NATIVE_OVERWRITE_OLDER$ pre-defined variables control how the native code setup engine handles errors and overwrites during native code installations.
The new $NATIVE_LOGGING$ and $NATIVE_ROLLBACK$ pre-defined variables control whether the native code setup engine permits uninstallations and rollbacks of native install actions.
The new $RECOMMENDEDUPGRADE$ and $NATIVE_OLDLOG$ pre-defined variables indicate if and where an old setup using the native engine was found on the target system.
Setup User Interface
Images may now be loaded onto dialog controls at runtime as follows: Define a script variable that has the same name as the target TImage control on your dialog. Before showing the dialog, set this variable to the full file system path of the image that you wish loaded onto the control (such as a file in $SUPPORTDIR$, or a file installed/already present on the target system). If the variable is not defined in the script or does not contain the full path of a file that exists, the existing image will be used and no new image will be loaded.
New Scripting Commands
The new Break and Continue commands allow for immediately terminating or continuing to the next iteration of repeat and while loops.
The new Reboot and Login command restarts the target system and resumes setup after the Windows shell has been loaded, complementing the Reboot and Resume command which restarts the target system and resumes setup before the Windows shell has been loaded.
The new Repeat and Until commands allow for the construction of repeat loops.
The new While and Wend commands allow for the construction of while loops.
Updated Scripting Commands
The Get System Settings command now supports obtaining the exact resolution of the target system display, as well as obtaining the exact amount of physical RAM installed.
The Install Files, Install Assembly, Install Service, Install ODBC Driver commands now support relative path names and environment variables for source file paths. All paths are relative to the root project folder.
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
Re: InstallAware 10
No changes to the translation system?
For example Unicode and finer resolution of translation importing.
For example Unicode and finer resolution of translation importing.
Re: InstallAware 10
Any of these items?
InstallAware Feature Requests
1. Have the Localization Wizard remember the folder last used for the associated project.
2. Be able to scroll through the script windows when running the setup debugger.
3. Dialog editor should default to project folder when selecting Open.
4. Dialog editor is positioned under task bar when task bar is positioned on left side of monitor.
5. Add a build manager. This would allow having lists of various builds and associated settings. It would also allow you to specify compiler defined variable to allow custom builds.
6. Use same character case (combination of upper and lower) in watch variables as used in the script.
7. Switch to Unicode for localized text strings. Remove the need for code pages.
8. Allow the return of the selection index of a drop down list and not just the selected text in custom dialog box drop down list objects.
InstallAware Feature Requests
1. Have the Localization Wizard remember the folder last used for the associated project.
2. Be able to scroll through the script windows when running the setup debugger.
3. Dialog editor should default to project folder when selecting Open.
4. Dialog editor is positioned under task bar when task bar is positioned on left side of monitor.
5. Add a build manager. This would allow having lists of various builds and associated settings. It would also allow you to specify compiler defined variable to allow custom builds.
6. Use same character case (combination of upper and lower) in watch variables as used in the script.
7. Switch to Unicode for localized text strings. Remove the need for code pages.
8. Allow the return of the selection index of a drop down list and not just the selected text in custom dialog box drop down list objects.
Re: InstallAware 10
DifX version updated
Visual Studio Add-Ins now check for strong named keys on assemblies before deciding to use Install Assembly instead of Install Files
Visual Studio Add-Ins now do better filtering of core .NET libraries from setup inclusion
"If Variable X Contains $" miabuild.exe command line build error fixed
The MAX_PATH path length is now being transcended by the build process
Get Folder Location GUI vs. MSIcode index discrepancy fixed
Windows Installer Engine: ControlService causing uninstall failures fixed
Windows Installer Engine: ControlService service stop and removal action failures fixed
Premature reboot on .NET 4 runtime installation fixed
Remove Unpinned Assemblies command fixed to work on .NET 4
InstallShield import bugs fixed, native conversion for more project settings added
Wise import bugs fixed
Install Assembly, Install Service, and Install ODBC Driver commands now use Install Files type folder naming semantics, fixing path length issues
Windows Installer Engine: A setup in 64 bit mode can now properly write to the 32 bit registry in addition to the actual 64 bit registry.
Visual Studio Add-Ins now check for strong named keys on assemblies before deciding to use Install Assembly instead of Install Files
Visual Studio Add-Ins now do better filtering of core .NET libraries from setup inclusion
"If Variable X Contains $" miabuild.exe command line build error fixed
The MAX_PATH path length is now being transcended by the build process
Get Folder Location GUI vs. MSIcode index discrepancy fixed
Windows Installer Engine: ControlService causing uninstall failures fixed
Windows Installer Engine: ControlService service stop and removal action failures fixed
Premature reboot on .NET 4 runtime installation fixed
Remove Unpinned Assemblies command fixed to work on .NET 4
InstallShield import bugs fixed, native conversion for more project settings added
Wise import bugs fixed
Install Assembly, Install Service, and Install ODBC Driver commands now use Install Files type folder naming semantics, fixing path length issues
Windows Installer Engine: A setup in 64 bit mode can now properly write to the 32 bit registry in addition to the actual 64 bit registry.
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
Re: InstallAware 10
> "If Variable X Contains $" miabuild.exe command line build error fixed
it is not fixed. I've just stopped on it during port to latest IA10.10 (Mooya.beta.311210)
Is any workaround for it? ReadRegistry do not help me - I need the error flag.
regards
Jarek
it is not fixed. I've just stopped on it during port to latest IA10.10 (Mooya.beta.311210)
Is any workaround for it? ReadRegistry do not help me - I need the error flag.
regards
Jarek
Re: InstallAware 10
Dear Jarek,
Please regenerate and reinstall your license and let me know if the problem still exists.
Please regenerate and reinstall your license and let me know if the problem still exists.
Aviv Giladi
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: InstallAware 10
Hello,
I've tested it and problem remains....
Installer was build by commandline script.
InstallAware MSIcode Compiler (Mooya)
Copyright(C) 1996-2011 InstallAware Software. All rights reserved.
Source File : my_checkOfficeDrv
Line Number : 11
Compile Error: Variable not defined: $DOLLAR$
regards
Jarek
I've tested it and problem remains....
Installer was build by commandline script.
InstallAware MSIcode Compiler (Mooya)
Copyright(C) 1996-2011 InstallAware Software. All rights reserved.
Source File : my_checkOfficeDrv
Line Number : 11
Compile Error: Variable not defined: $DOLLAR$
regards
Jarek
Re: InstallAware 10
Dear Jarek,
Could you please send the reproducing project with a more accurate description of the problem to support @ installaware.com?
Thanks!
Could you please send the reproducing project with a more accurate description of the problem to support @ installaware.com?
Thanks!
Aviv Giladi
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: InstallAware 10
Dear InstallAware users,
This seems to only happen when the check for the dollar sign is inside an included script.
As a workaround, define a variable called DOLLAR in the main script and set it's value to $.Then, in the included script, check if a variable contains $DOLLAR$ instead of the explicit dollar sign.
This seems to only happen when the check for the dollar sign is inside an included script.
As a workaround, define a variable called DOLLAR in the main script and set it's value to $.Then, in the included script, check if a variable contains $DOLLAR$ instead of the explicit dollar sign.
Aviv Giladi
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: InstallAware 10
> This seems to only happen when the check for the dollar sign is inside an included script.
yes, exactly
> As a workaround [...]
thanks
regards
Jarek
yes, exactly
> As a workaround [...]
thanks
regards
Jarek
Who is online
Users browsing this forum: No registered users and 36 guests