Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

Install to Preexisting Location

3 replies to this topic


  • Members
  • 2 posts

Posted 19 September 2002 - 20:32

I'm trying to install a component (MSWord template) to Word's startup folder.
I've setup a AppSearch item looking for the registry value, but the property never gets the value. Thus, the component is installed to [TARGETDIR].

Using InstallShield Developer 7.04

Any ideas on how to accomplish this?


  • Full Members
  • 532 posts

Posted 23 September 2002 - 23:37

All you should have to do is setup the appsearch table correctly. This should then set a property, which you then must use as your destination for your component.


  • Members
  • 2 posts

Posted 23 September 2002 - 23:42

Sounds easy enough, doesn't it?
I've tried setting it up according to the documentation, I've done it using the wizard, I've tried it in what seemed to be a logical manner, and I've even tried setting it up unlogically. All to no avail.

Can you give step-by-step instructions for setting it up correctly?


  • Members
  • 227 posts

Posted 01 October 2002 - 17:01

Thsi is a sample.
1. AppSearch table:
Property      DESTDIR (upper case)
Signature     DestDir

2.  RegLocator table:
Signature     DestDir
Root           2      (HKLM)
Key            Software\....
Name          ValueName
Type           0  (to get a path)

3.  Directory table
Directory              DESTDIR
Direstory_Parent    TARGETDIR
Default_Dir            .

Then set a component destination as [DESTDIR].

You can create a simple custom action to show this property to make sure it is set correctly. It is easy with VB script.
Custom action Type  102
Source   (empty)
Target   MsgBox "DESTDIR = "  & Session.Property("DESTDIR")    

Insert this custom action after AppSearch

Good luck,
Irina Shirinsky
Software Engineer, Heroix Corporation