About hviolet

hviolet · ‎Jan 14, 2016

Installshield 2014 Basic MSI Hi All, Our project contains merge-Modules. Building from Installshield works. Now we definitely want to build via TFS. In this case, build fails with error "the path is longer than the limit set by the os" or so. Actually the path that is in question has about 182 characters. Where lies the origin of the path restriction. Why is it so short (in Windows-Explorer, I have been able to create much longer paths)? What is the recommended strategy for TFS-Build? Note: when building from TFS, the dest folder structure is longer than that, when building from Installshield. It is like c:\builds\MyBuildDefinition\src\MyInstallshieldProject\MyConfiguration\MyRelease instead of c:\MyInstallshieldProject\MyConfiguration\MyRelease We are not inclined to call our BuildDefinition "B" and our BuildConfiguration "C" and so on. Thanks for any help. H.

hviolet · ‎Nov 23, 2015

This had nothing to do with the Suite Setup! The Problem was produced by the msi-package, which afforded a restart (independently of the Service update).

hviolet · ‎Nov 23, 2015

(Installshield 2014 Suite-Project) Hi, An msi-Package of our Suite-Setup installs a windows-Service. The msi contains the logic to stop the Service on install. Now if the Suite-Setup is installed as an update (the Service will be updated), it Claims a restart of the Computer, which I would like to prevent. When stopping the Service manually before the Suite-Update, no restart is necessary. Regards, Heiner.

hviolet · ‎Nov 20, 2015

Thank you Dan for your reply, I have noticed, that a suite setup automatically performs an update if there is installed a previous version. We introduced the version check to inform the user, that an update will take place. As to the ProductVersion property I was looking for, this property exists and can be used during the setup - it is only (to my knoledge) not documented in the suite property reference. Regards, Heiner

hviolet · ‎Nov 18, 2015

(Installshield 2014 Suite-Project) Hi, is there a Suite-Property that is set if and only if the Suite-Setup is performing an update? Is there a Suite-Property containing the productVersion defined unter General Information? At the Moment, I'm trying to set my Own Update-Property. This property is set if the uninstall key for the Suite in the Registry exists but has DisplayVersion lower than the Version specified under General Information. Now in the condition of the set Property Action, I have to reenter the product Version. Thanks for your help, Heiner.

hviolet · ‎Nov 06, 2015

(Installshield 2014 Suite-Project) I'm using a powershell-Action to pop up a MessageBox. The Action is scheduled under OnPackagesConfiguring. The MessageBox is indeed opened - BUT it is hidden by the Wizard-Dialog (Installation Progress). (Note: in my simple test the PS-Action does nothing more than showing a MessageBox) Any help will be greatly appreciated.

hviolet · ‎Nov 06, 2015

Thanks for your advice. Calling a Set Property Action immediately after the Instalscript Action works. The textbox is updated. After being updated, the input Cursor is automatically placed at the first Position.Is there a possibility to control the Cursor postion in a textBox? (We aim to add some stuff characters while the user makes his Input - like the delimiters of a Key xxx-xxx-xxx.) If not - is it possible to put ones own textField control on an Installshield Dialog? regards, H.

hviolet · ‎Nov 05, 2015

Thanks for the reply. We have packages that are associated to some Features but not to all. For These packages I introduced a new parent-Feature that has the needed Features as Subfeatures. Setting this parent-Feature invisible makes the child Features also invisible - so it has to be visible.

hviolet · ‎Nov 05, 2015

(IS 2014 Suite-Project) Thank you for the replies. In my opinion a Feature that is not installed should be entirely un-checked in the Feature-selection Dialog during maintenance (Modify). The setup-user doesn't know anything about packages. Introducing parent Features as you mentioned brings the desired effect but increases the number of visible Features. Next question: I would like to Show a Wizard Dialog only if a certain Feature has been selected (first time install). Which property can be used for the dialogs 'visible' condition?

hviolet · ‎Nov 04, 2015

(Installshield 2014 Suite-Project) In maintenance mode (modify installation), a Feature, that is not yet installed, has an indeterminate Checkbox, if an underlying package is already installed. Details: In a suite-Project are two features A and B. There are three packages p1, p2, p3, that are associated to features in the following way: A <- p1, p3 B <- p2, p3 That means p3 is associated to both Features A and B. (In our design, package p3 provides some core-functionality, needed for several features) Now, in the first time Installation I choose only Feature A to be installed. OK Launching setup again in maintenance mode and choosing 'Modify' shows this selection of features: A checked (correct, because Feature A is already installed) B indeterminate (a filled Checkbox, neither checked nor unchecked) Why is this so? Feature B is not yet installed though package p3, that is associated to B, is. Obviously the Default selection of Features in maintenance mode is dependendant of the Installation of underlying packages. Would it not be better to make the Feature selection independant of underlying packages? Is it possible to achive that? Thanks for any help.

hviolet · ‎Nov 03, 2015

(Installshield 2014, suite-project) On a wizard dialog I have tied the enabled state of the next button to the value of a property (property comparison). When the property is directly changed via another control, e.g. a checkbox, the state of the next button is immediately updated (from disabled to enabled or vice versa). BUT when the property is changed via a suite action, the state of the next button remains unchanged. This is independant of the action type (I tried Installscript and powershell actions). The same problem: we need to change the content of a textbox via suite action. Here, a change of the property value the textbox is bound to is not shown in the textbox unless going next and back in the dialog order. Is there a way to force the dialog to reload its content. Do I have to call a Windows API function? Thanks in advance.

hviolet · ‎Sep 28, 2015

Thank you MichaelU for the reply, Yes I meant exactly that run-time error you mentioned. I have found a workaround that allows checking for empty/non-empty Registry-String-values: Compare to: , where P is a property with empty value - that works.

hviolet · ‎Sep 26, 2015

[IS 2014, project type Suite/Advanced UI] Hi, I'm trying to create a registry comparison that checks that a certain string value under HKLM\Software\... is not empty. (The comparison serves as a detection-condition for feature X.) PROBLEM: It is obviously not allowed to leave the "Compare To" field empty. The error is simply something like "please enter a value to be compared to". Operator: Any Condition Check: Registry Comparison Registry Key: HKLM\Software\... Value name: Conversion: String Comparison: not equal Compare To: should remain empty ... Is there a trick I'm missing? Any help will be greatly appreciated 🙂

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Merge-Module Path too long, TFS Build

Re: service-update via msi-package, suite-setup wants restart

service-update via msi-package, suite-setup wants restart

Re: Suite-Property indicating product update, ProductVersion Property

Suite-Property indicating product update, ProductVersion Property

Messagebox hidden by Wizard-Dialog

Re: Property change not reflected on wizard dialog

Re: maintenance-mode: default selection of features is confusing

Suite-Property for selected features

maintenance-mode: default selection of features is confusing

Property change not reflected on wizard dialog

Re: Suite-Project - Registry Comparison condition - Empty string

Suite-Project - Registry Comparison condition - Empty string