Adding the install path to a registry key

devinr1.552492868189645E12 asked a question.

July 8, 2008 at 3:07 AM

I'm currently trying to create a key in the registry that will hold the install path selected by the user during installation. This will be used to discover whether the program has been installed before, and more importantly where it has been installed.

The only problem is, that I'm not entirely sure how to go about implementing this using InstallShield 2008 Express. Any advice on whether this is possible and how I'd go about setting it up in the program would be greatly appreciated.

InstallShield

community.dx1.5524945332986533E12
18 years ago
To store the install path in the registry, you'd want to add the required registry keys in the Registry view of your project. You could enter [INSTALLDIR] for a registry value. At run time, Windows Installer would replace [INSTALLDIR] with the path of your installation.

I don't think that you'd need to do this in order to simply determine whether your product has already been installed. When the end user launches your installation, Windows Installer will automatically search the target system to see if the product is already installed, as described in the following thread:

http://community.acresso.com/showthread.php?t=181956

Does that help?
Expand Post
aguest1.5524923028085112E12
18 years ago
I ran into the same issue; I needed to try and prevent IS installing over an existing installation since the user is free to type in whatever path they want in the Destination Folder dialog. Like me you don't so much want to know if it is already installed, rather, where. What i ended up doing was calling out to a Custom Action .exe that I wrote , After Destination Folder Dialog. THis exe just scans the folder chosen for some well known files and if it finds any then i assume the user has picked an old installation folder. Then i throw up a mesagebox to warn them (which you must force on-top BTW). I set IS to ignore the return code and wait for the action to complete. All you can do is warn the user and tell them to press 'Back' in the wizard that follows. If you tell IS to take note of the return code you will see an annoying error message. And that means I had to then introduce a superfluous "Ready to Install" dialog into the wizard to allow a BAck action. This is a really fundamental thing - IS Express has obviously been cut back severely to get you to buy Premier or Professional. It's really just for shareware installations i reckon, no good for serious business apps.

Hope that helps, Andy
Expand Post

Related Questions

Nothing found

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Related Questions

Trending Articles

Please wait...

Case id: 00001065