Adding a file to Office folder

Create system search for your directory value, with operation "read file pathname from registry", and assign the result to property INSTALLDIR.

Do this in the installation:

add some arbitrary directory under program files, for example name it OfficeDir
put the file you want to install into Office directory in that arbitrary directory
open setup editor, and open table Directory
find the row with your OfficeDir in the column DefaultDir
take the value of the column Directory - that's the name of the property associated with the directory.
In your system search, use that property name instead of INSTALLDIR.

This worked for me in Wise, should work in Installshield as well (which I avoid).

If for some reason this does not work, another way is to create new feature just for this file. Features normally have their own installation directories, so for this feature the same method must work. You can make that feature hidden.

> I can't use INSTALLDIR for two different directories can I?

no, you can't.

objection. The asker was given precise steps to resolve the problem. What he did is probably the same (adjusting for the not very clear explanation, see below), too bad he does not even understand that.

Besides, his explanation can't be accepted as solution because:

1. components are not created under files and folders. In Installshield, they are created under organization/components.

2. system search does not deploy anything anywhere. However, component's destination can be specified as property, which in turn was the result of system search - this is probably what the asker did.

1. this may depend on the interface of specific installshield product. In mine, there's no such option.

2. No, system search still does not install anything. That your installshield gives you this option means the exact same thing that I have suggested: use the property as destination.

No unnecessary folder would be created on client's pc. The substitution of the property for the actual folder name would occur before the actual installation. Rather than making assumptions, you might have tried what I suggested - unlike you, I have verified it before making the suggestion.

Accordingly, the answer to point number 2 was "put the file you want to install into Office directory in that arbitrary directory".

Effectively, you have done exactly the same thing as I suggested, only you used different buttons: you performed system search, put result into a property, and  used that property as destination for the directory. It's good news that you found those buttons in your specific version of installshield, but it does not mean that what I said was irrelevant.

Since you have moved into the territory of personal insults (although I don't see where was insult in my objection), this is my last comment in this thread.

I still object to this disposition. The reason: the solution I proposed is 100% equivalent to the solution of the asker. The difference is only in the interface of particular tool used to create the installation; I said that the solution worked in Wise where I verified it, and should work in Installshield as well. What the asker did was: he did find the way to do it in Installshield. But the essence of the solution remains the same: do system search; put result in a variable; use the variable as destination for the folder where to put the file.

The system search in itself does not install anything. It returns the result in a property, and that property subsequently can be used anywhere during the installation.  Installshield interface for system search provides checkbox "use this property as destination", so the asker thinks that it is fact one operation.

Maybe it would be good idea if this dispute was reviewed by someone familiar with Windows Installer.

> It's like asking for a solution for Microsoft Office and you giving a solution for Open Office.

this depends on what to call a solution. This is in fact great analogy with Office. For example, you ask how to make next word to begin from the new line, and I respond that you have to begin new paragraph, but I don't tell you what exact button to push in Word. Meanwhile, you do little research in Word and find out that you have to press Enter. The next thing you say is that this is your solution because it's not new paragraph that begins new line, but enter key. This is the exact thing that is happening here, and not even once. For example, your another  discovery: "I found out how to create a new property although not very documented. When you create a system search, just type in a new property name..." is 100% equivalent to my very first comment "assign the result to property INSTALLDIR." - yes, I did not say "type", same as I wouldn't say "press enter key"...

As for the system search... let me use another analogy. Let's say, you go to a web site where you have to sign up for an account. Near the userid and password fields, there's checkbox "remember me on this computer". If you check it, the next time you will be logged on automatically. But it's not this checkbox that logs you in, and not the sign-up screen. Both only prepare the information for the subsequent logon - you still have to navigate to the link "log into my account". The same is happening here. System search generates the rows in the table AppSearch for the installer and puts action AppSearch in the script. The result of it goes to the property, which is the destination of the component. But the installation itself is made by ExecuteActiion, which happens much later, and takes into account many other things. If you make the feature the file belongs to optional, and the user does not select it during the installation, then the file will not be installed, even though the system search was performed - same as if you checked "remember me on this computer" during sign-up, but then never came back to the website. If the installation relies on certain condition, or registration key entered by the user, it won't be installed. Finally, if the user simply presses "cancel", it won't be installed. All these things happen during the installation after system search was already performed, and all would not be possible is system search itself installed something.

I truly suggest that you take some time and learn more about Installer rather than only Installshield, so you see not only the steering wheel and gas pedal, but also have in mind the engine - it does help to drive.

>"I found out how to create a new property although not very documented. When you create a system search, just type in a new property name..."  isn't 100% equivalent to your answer as INSTALLDIR couldn't be used.

My answer was not the INSTALLDIR could not be used. It was that INSTALLDIR can't be used for two different directories - that's what you asked. The keyword is "different".

INSTALLDIR is only one property. Whatever property you type in there, becomes the result of the search. If that property did not exist before, then it's automatically created at this point. So if you type there MYPROPERTY, this creates new property MYPROPERTY and put the result in it. Then you have to tell that you want to use new property as the destination of the directory. One way to achieve that is by the steps that I provided - which would work in any MSI editor (even the same Installshield may have different faetures, for example Standard vs. Professional). But each editor can offer other ways to do that , and it's good that you have found more user-friendly one in your Installshield.