About ussraf

ussraf · ‎Jan 22, 2010

Thank you. This let me know what can be done and what not..:p

ussraf · ‎Jan 21, 2010

MichaelU wrote: Assuming you're asking if there's a way to specify these names, rather than if there's a way to change them dynamically at installation time, yes. Select each feature in the Setup Design or Features view of the Installation Designer, and edit the Display Name property. If you're asking about doing this dynamically, I don't think there's a good way for a Basic MSI project, but there may be one for InstallScript setups. See FeatureAddItem and its example for an idea down that road, if you're using an InstallScript project. Oh, yes, thank you Mike, I'm actually asking the second - dynamically. The only one idea I can have is using the setup.exe, i.e. when setup.exe has extracted the .msi I use some MsiOpenDatabase() call to change the .msi database first. However, it wasn't that possible for I don't see anyway that I can modify the setup.exe generated by InstallShield IDE or adding some callbacks to that.

ussraf · ‎Jan 21, 2010

Hi, Any anybody knows when in a property {String1} is resolved to the real value of the string "String1" and in a string [Property1] is resolved to the real value of property "Property1" Thanks.

ussraf · ‎Jan 21, 2010

Hello, Is there an easy way to change the feature's display name in runtime? Thanks.

ussraf · ‎Jan 11, 2010

Yeah, agree and thanks. Also found some post about 64bit install in MSDN. http://msdn.microsoft.com/en-us/library/aa372855(VS.85).aspx

ussraf · ‎Jan 11, 2010

TsungH wrote: There is a typo in the condition. :eek: :eek: :eek:

ussraf · ‎Jan 07, 2010

Hello, My project is going to provide 2 different set of files for 64bit windows and 32bit windows. So I'm not sure if there are any best practice on them. Is there a way to provide a single installer that allow install different set of features/components conditionally? Is that a good way? And if some user has installed my 32bit stuffs(they are runnable in 64bit environment although not good enough) using 32bit installer, and later some day they'd upgrade them to 64bit, what's my option to make the old 32bit stuffs removed and 64bit installed? Thanks.

ussraf · ‎Jan 06, 2010

Hi, it's me again.. I got a problem to hide a checkbox in SetupCompleteSuccess, I want to hide that checkbox if the system is Windows 7 64bit. I added 2 entries in Conditions table: Entry 1 -- Action: Hide Condition: VesionNT64>=601 Entry 2 -- Action: Show Condition: NOT VersionNT64>=601 But that checkbox always show regardless of the OS platform. Then I created a small testing InstallShield project and did the same thing, and it worked! However it still don't work in my production project. So anyone knows what can prevent the condition VersionNT64>=601 from functioning? Or is there some other reasons?:confused:

ussraf · ‎Jan 06, 2010

jaybee96 wrote: This is the correct one for your specific request...:) Feature: Install Level = 1 Display = Visible and .. Condition = level = 0 VersionNT64 Oh, nice, didn't see that the Condition in Feature section can control the level!

ussraf · ‎Jan 05, 2010

Hi, Anyone knows how to make the NewFeature2 invisible using some kind of conditions? For example, I actually want it to be invisible to user if this is an 64bit environment. Thanks

ussraf · ‎Nov 11, 2009

Holger_G wrote: If you have not, please refer to the INSTALLLEVEL Property. :eek: Nice..

ussraf · ‎Nov 11, 2009

Hi, A simple question. How can I make a feature(Feature2 in the attachment) by default "not available"? :eek:

ussraf · ‎Aug 21, 2009

RobertDickau wrote: Please see the MSI help topic "Examples of Conditional Statement Syntax"; there's an example for detecting a component reinstall that you should be able to adapt... 😄 Too good..

ussraf · ‎Aug 20, 2009

Hello, I know if &Feature1=2 is the condition that Feature1 is going to be removed and &Feature1=3 is the condition that Feature1 is going to be installed. But looks there is no value for a "reinstall". Also the way using REINSTALL> Any better way? Thanks.

ussraf · ‎Jul 17, 2009

Looks a related thread here: http://community.acresso.com/archive/index.php?t-181725.html Not sure if there are any updates on this issue?

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

Re: Runtime Change a Feature's Description

Re: Runtime Change a Feature's Description

How and When [] and {} are resolved?

Runtime Change a Feature's Description

Re: What's best practise for deploying a 64bit installer and 32bit installer?

Re: Hide A CheckBox in SetupCompleteSuccess Dialog for Win7 64Bit

What's best practise for deploying a 64bit installer and 32bit installer?

Hide A CheckBox in SetupCompleteSuccess Dialog for Win7 64Bit

Re: How to Conditionally Hide the Feature?

How to Conditionally Hide the Feature?

Re: How to Make a Feature Default Unavailable?

How to Make a Feature Default Unavailable?

Re: The condition to determine a feature is to be reinstalled

The condition to determine a feature is to be reinstalled

Re: ISCmdBld.exe return -1073741819

Re: Runtime Change a Feature's Description

Re: Runtime Change a Feature's Description

How and When [] and {} are resolved?

Runtime Change a Feature's Description

Re: What's best practise for deploying a 64bit installer and 32bit installer?

Re: Hide A CheckBox in SetupCompleteSuccess Dialog for Win7 64Bit

What's best practise for deploying a 64bit installer and 32bit installer?

Hide A CheckBox in SetupCompleteSuccess Dialog for Win7 64Bit

Re: How to Conditionally Hide the Feature?

How to Conditionally Hide the Feature?