This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Autiomation interface cannot set all properties for new release.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2010
07:37 PM
Autiomation interface cannot set all properties for new release.
😞
We use IS 2010 Automation interface (ISWiAuto16), but it is seriously out of date with respect to IS 2008 project options, and does not support property assignment for releases targeted for current Microsoft Platforms.
Each automated build of our products requires in increment in the release version, which is reflected in the Release name. Since the automation interface does not allow re-name of an existing release (the "Name" property of a relase is Read Only), it is not possible to use a pre-built release configuration as a template, and a new release must be created on the product configuration.
However, for Windows 2008 and Windows 7, our release must use a elevated privilege, so we need to set the "Required Execution Level". property for Setup.exe. The automation interface does not support access to this property, and there is no other way to modify the manifest that IS embeds in the Setup.exe launcher. How else can this property be set without using the IDE?
From the IS documentation, it appears the only way this property can be set is through the IDE, which makes the automation interface worthless. Dumb!
Dave Phillips
Honeywell Inc.
We use IS 2010 Automation interface (ISWiAuto16), but it is seriously out of date with respect to IS 2008 project options, and does not support property assignment for releases targeted for current Microsoft Platforms.
Each automated build of our products requires in increment in the release version, which is reflected in the Release name. Since the automation interface does not allow re-name of an existing release (the "Name" property of a relase is Read Only), it is not possible to use a pre-built release configuration as a template, and a new release must be created on the product configuration.
However, for Windows 2008 and Windows 7, our release must use a elevated privilege, so we need to set the "Required Execution Level". property for Setup.exe. The automation interface does not support access to this property, and there is no other way to modify the manifest that IS embeds in the Setup.exe launcher. How else can this property be set without using the IDE?
From the IS documentation, it appears the only way this property can be set is through the IDE, which makes the automation interface worthless. Dumb!
Dave Phillips
Honeywell Inc.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 23, 2011
11:52 AM
IS 2011 Automation Interface (ISWiAuto16) still does not allow to set the "Required Execution Level"
.. or perhaps that the documentation has not been updated.
I use ISWiRelease object, but I found no way to set this property 😞
Does somebody have some information about that ?
Thank
.. or perhaps that the documentation has not been updated.
I use ISWiRelease object, but I found no way to set this property 😞
Does somebody have some information about that ?
Thank
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 30, 2011
11:08 PM
jarcinfo wrote:
IS 2011 Automation Interface (ISWiAuto16) still does not allow to set the "Required Execution Level"
.. or perhaps that the documentation has not been updated.
I use ISWiRelease object, but I found no way to set this property 😞
Does somebody have some information about that ?
Thank
InstallShield 2012 support it.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)