About John-H

John-H · ‎Jul 19, 2012

Flexera support say the condition builder UI needed is not available in Express. I might have a workaround though... Firstly, build the project without signing the setup.exe or msi files and then use Orca to build a transform containing the condition changes I need. Then in the build batch file… o build the project without signing the setup.exe or msi files o use msitran to apply the transform to the msi file o sign the setup and msi files with signtool This should work as long as there is no significant change to the InstallShield project.

John-H · ‎Jul 12, 2012

I need to call a custom action when my product is being installed and when it is having a minor upgrade using the REINSTALL property. The action works fine during the initial install, but by looking at the logs I can see it is skipped during a REINSTALL. Using Orca I can see there is a ' Not installed ' condition against my action. Using Orca I can set this condition to ' Not installed or REINSTALL<>"" ' and now the action is called both during initial install and REINSTALL. Is there any way I can set this condition via the InstallShield 2012 Express user interface? My msi is built as part of an automated build process and I cannot go in and 'fiddle' the condition with Orca after every build. John

John-H · ‎Nov 03, 2009

I am getting the following errors when I validate my msi using Orca after building with InstallShield 2010 Express SP1 ICE18 ERROR KeyPath for Component: 'ISX_DEFAULTCOMPONENT' is Directory: 'INSTALLDIR'. The Directory/Component pair must be listed in the CreateFolders table. ICE18 ERROR KeyPath for Component: 'ISX_DEFAULTCOMPONENT3' is Directory: 'INSTALLDIR'. The Directory/Component pair must be listed in the CreateFolders table. I can get rid of them by manually adding entries in the Create Folder table (using Orca rather than Direct Editor as I have 2010 Express) and then I have to manually run signtool.exe on the msi. Because we automate our build process this is not an acceptable long term solution. Please could anyone give me tips on how to avoid these errors in the first place? And also how can I tell what elements the ISX_DEFAULTCOMPONENTs relate to? While our application installs fine I cannot ignore these errors as I did with InstallShield 2010 Express as we are trying to get a Microsoft "Works with" logo and these are preventing us from doing so.

John-H · ‎Feb 05, 2009

Please can anyone tell me how to get InstallShield 2009 Express to put a copy of setup.exe onto the server folder during an administrative setup (setup /a)? Thanks

John-H · ‎Dec 23, 2008

I just found this Microsoft article that confirms Michael's comment that this is a Windows Installer "feature". http://msdn.microsoft.com/en-us/library/aa368289(VS.85).aspx

John-H · ‎Dec 23, 2008

Thanks for everyone's help. Yes Michael, my aim is to be able to install to network client pcs from the server folder, either through group policy or direct client action but when that client is running Vista I don't want it to receive a message that it is running software from an unknown publisher. This is not actually a problem within our own organization but we are a software development company and I am currently writing a customer installation guide for our customers and need to detail for them how to achieve a trouble-free installation, or at least flag up any potential problems and document a work around. I think I understand the setup process better now. John

John-H · ‎Dec 22, 2008

I suppose I could just manually copy the uncompressed CD image to the server folder but wouldn't that defeat the idea of an administrative install? I thought the advantage of an administrative install was that it ran with the privileges of the user that ran the setup /a rather than the client user.

John-H · ‎Dec 22, 2008

Thanks for the suggestion. I have tried building the release uncompressed this but unfortunately it results in the same problem. The msi is signed in the CD image but not when installed with setup /a. The file sizes of these two msi files are the same to the nearest KB but the timestamps are different.

John-H · ‎Dec 22, 2008

I find that using a double ampersand && works in the name of one of my features so it might work in the name of your application

John-H · ‎Dec 22, 2008

I am creating a CD-ROM compressed installation with InstallShield 2009 Express. I have digitally signed the exe, dll, setup.exe & msi files. On the cd image these (and the cab file) are all signed correctly. However if I subequently use "setup.exe /a" for an administrator install to a server folder the setup installs correctly but the msi file on the server is NOT digitally signed (all the exe and dll files are) Anyone have an idea how I can get the msi on the server to be signed as this is the msi that will be used for all network client installations, many of which are Vista? John

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

Workaround

Custom action during REINSTALL

ICE18 errors

Setup.exe does not get copied during setup /a

Re: Setup /a does not digitally sign msi file

Thanks again

More thoughts

Thanks

Try &&

Setup /a does not digitally sign msi file