You can disable the change remove and repair buttons to show up in Add/Remove programs in the General information->Add or Remove programs. To affect the maintenance options that come up when rerunning the exe, you could edit the maintenance type dialog directly, although the user could still run a repair by using MSIEXEC.exe command line parameters, or by Windows Installer repairing automatically. ... View more

Hi, In Installshield Express 2014, the bitmap image at the very beginning of an installation must be 440 x 275 pixels. However, on what seems to be quite "normal" resolutions, that image is shown as 580 x 350 and in a poor quality. It's a pity, because this could be a way to personalize installations with a good photograph and text. In the beta-version of 2015 I don't even find the way to enter the name of my bitmap, but projects converted from 2014 show the same resul: the image is resized in a bad quality. I have tried in version 2014 to use images larger than 440 x 275, but it doesn't work. Have you, Eladef, ever got an answer, or has anyone had the same problem and found a solution? ... View more

Sorry didn’t understand you suggestion Currently I have shortcut AAA associated to feature A, now If feature A is installed I need shortcut name to be AAA If feature A and B are installed I need shortcut name to be BBB (without AAA) ... View more

Another way to do it is to use Automation Interface to make non-persistent changes (associating components in Feature A to Feature C) during build time. ... View more

Did you look for conditional expression something like "&MySubFeature=3" and display some message on push button if not selected ... View more

Your question is confusing. 1. Define what you mean my 'Reinstall'. An Unistall, followed by an Install if often termed a Reinstall, but it shouldn't operate any different that a 'Fresh Install' unless you have left behind some permanent files. Are you talking about a 'Repair'? 2. Where are you trying to add these condition statements? To the CA or the Feature? 3. Please explain more clearly what you are trying to do. ... View more

I don't how/if this would work in a Basic MSI project, but this is how I get it to work in InstallScript MSI. It takes the value of INSTALLDIR, clips off the last folder and replaces it with "MyFeature": 1) Set the Feature/Component Destinations for the feature(s) you want in "C:\COMPANY\DIR2" to a directory identifier called INSTALLDIR_MYFEATURE with some fake value (ex ##INSTALLDIR_MYFEATURE_FAKE##) 2) After Dlg_SdAskDestPath is called (where the user determines where they want your program installed), call this custom function by passing it the regular INSTALLDIR string: Prototype: prototype STRING MyFeature_GetMyFeatureInstallDir( byval STRING ); // szInstallDir Function: function STRING MyFeature_GetMyFeatureInstallDir( szInstallDir ) LIST lstInstallDir; STRING svMyFeatureInstallDir, svPathPart; NUMBER i; begin lstInstallDir = ListCreate( STRINGLIST ); // determine what value INSTALLDIR_MYFEATURE should have: StrGetTokens( lstInstallDir, szInstallDir, "\\" ); svMyFeatureInstallDir = ""; for i = 0 to ListCount( lstInstallDir ) - 2 ListSetIndex( lstInstallDir, i ); ListCurrentString( lstInstallDir, svPathPart ); if svMyFeatureInstallDir != "" then svMyFeatureInstallDir = svMyFeatureInstallDir + "\\" + svPathPart; else svMyFeatureInstallDir = svPathPart; endif; endfor; svMyFeatureInstallDir = svMyFeatureInstallDir ^ "MyFeature"; MsiSetProperty( ISMSI_HANDLE, "INSTALLDIR_MYFEATURE", svMyFeatureInstallDir ); return svMyFeatureInstallDir; end; 3) the following line from that function is what sets the correct value for the Feature/Component destinations: MsiSetProperty( ISMSI_HANDLE, "INSTALLDIR_MYFEATURE", svMyFeatureInstallDir ); Again, I don't work with Basic MSI projects but hopefully this will give you an idea of how it can be done. HTH ... View more

Eladef, we want to do the same thing and I would like to know how you have made out on this? Also since IS 2011 only has the Microsoft Office 2007 PIA.prq, where did you get the one for 2010? Would you be able to supply the one you have or let me know where you found the 2010 one? Thanks, ... View more

Hi, Try using a launch condition for SETUPEXEDIR property. This property only gets set when run from Setup.exe. Hence, it will cancel the setup, if run from msi. I hope this helps! ... View more

In the value filedl of Regitry you can give like [COMPANYNAME] so it will updated with the value available on the property COMPANYNAME ... View more

Could you post the code? A quick InstallScript test with a missing source file--- function OnBegin( ) NUMBER ret; begin ret = XCopyFile(WINDIR ^ "no-such.file", TARGETDIR, COMP_NORMAL); SprintfBox(INFORMATION, "XCopyFile result", "ret = %d\nMsg = %s", ret, FormatMessage(ret)); end; ---displays a message box with: nvIgnore = -2147024894 Msg = The system cannot find the file specified. ... View more

There's no need to spin up a custom action for this sort of thing. A condition to check that you're running on (at least) Windows Server 2008 R2 should look like VersionNT >= 601 AND MsiNTProductType > 1 whereas a check for exactly Windows 7 that excludes Server variants should look lik VersionNT = 601 AND MsiNTProductType = 1. To check for a 64-bit OS, substitute VersionNT64 for VersionNT. To require a 64-bit OS, consider changing the template summary, although that yields control of the message to Windows Installer. ... View more

Have you kept your Major Upgrade settings to "Completely uninstall older setup...". If not, try that way. It must clear your old files. ... View more

Does someone has a creative idea about it ? ... View more

How about creating your own exe that simply launches PowerShell script. You can then use that exe in a prerequisite and also include scripts in the same prerequisite... ... View more