Installer executable name different from Product Name?

[jhndnn]

I was asked to add a check in our installer to make sure the user isn't currently running a copy of or software. This seemed fairly simple using the 'Check for Process' step - I just need to look to see if my executable is running and then ask the user to close it.

The problem is that the application executable is the same name as the Product Name in the installer. When the installer is compiled it automatically names the installer executable the same as Product Name. Since I'm creating a 'Single File' installer, the main installer executable is packaged up before I can rename it ( and it would probably break things if I did, anyways ).

So is there a way to decouple the Product Name from the executable generated by InstallAware? Should I use a different technique to tell if my application is running? Or just give up and rename the application exe?

[MichaelNesmith]

You can rename your MPR file, or you can simply choose a custom output file name.

[ALive]

Hi!

Yeah, i use the second variant as Michael describe. Moreover it's very good way to provide the name from outside. Just type the Compiler Variable like: #OUTPUTFILE# inside Output File Name text box, and initialize this variable (#OUTPUTFILE#) with the proper name, and here we go. The big plus of this solution, is that you can initialize this name from miabuild.exe tool on the Automation Build process.
For example, we make our names like: ProductName-xxx.xxx.xxx.exe Where xxx - is the version number which is came from Automation Build Service. Renaming *.mpr file would give us a headache, and lot's of time waste. So i find the solution with providing "Output File Name" more suitable.

Hope this helps!

[kebrite]

Hi,

After applying the R2 upgrade the "miabuild.exe" file is not installed so now my command line build fails. How do I do it from the new R2 release.

Thanks
Brendan

[MichaelNesmith]

Hi Brendan,

You also emailed about this issue. I told you that miabuild.exe won't get installed unless you've done a full install. You remain confident that you have indeed done a full install and still not gotten the miabuild.exe setup file installed, and my email offer to you still stands:

Send me a video of you doing a full install of InstallAware 9 R2 and the command line build tool not getting installed; and we'll give you a free upgrade to InstallAware Studio Admin 9 R2 with 2 years maintenance and floating license.

I am not sure how else to convince you that you have not done a full install.

[kebrite]

Hi Michael,

Well the file (miabuild.exe) was in the installer when selecting the full install option as you mentioned. Due to it not being in the default setting of minimum install, it was missing during my upgrade. Why is this not included i the minimum install as to get it I had to download the whole 1.5 Gig single file to get a file of 9 meg?

Anyway, all that aside now, when I execute the exact same batch file (contents below) the built promptly stops with the error in the attached screenshot. Why does it report more file missing even with the full install?. May be I should get that free upgrade that you offered after all! I ran the batch file bfore the upgrade just to make sure that it worked, and now it doesn't. Any suggestions?

Here is the batch file contents:
--------------------------------------------------------------------------------------------------
"C:\Program Files\InstallAware\InstallAware 9 R2\miabuild.exe" "C:\Projects\Kebrite\head\SystemInstallation\InstallAware\SolutionInstall\ SolutionInstall.mpr"
pause
--------------------------------------------------------------------------------------------------


Thanks
Brendan Keyhoe
Kebrite Solutions Inc

[MichaelNesmith]

You didn't have to download the full single file install; you could have just re-run your existing installation in maintenance mode to add just the command line build module. This would have downloaded just that bit.

Your project contains a hard-coded reference to an InstallAware 9 path for an include script. Not sure how that got in there, but you can update the .MPR file in Notepad to update the path to the new install location.