david every

Sajan.
Yes I understand what you are saying, and yes the idea is
simple. Other people are telling me that just assigning
the propertyname as uppercase exposes it as public,
whereas you are telling me that I have to assign a public
property to the control. I have tried the uppercase thing
and it doesnt expose the property as public. (I have a
tool that lists public properties in MSI's) Anyway if you
have a small C# project that shows your method I would
appreciate that, otherwise, I will try to get it going
myself.

Regards
David E


The idea is

assign a global property

the InstallExecute

config file.

kallely sajan

Did you see the other comment I made on 07/15/2003

--

Regards,
Sajan.

PS: Please don't send me direct emails, use the newsroom.

david every

OK I will do that, thanks for the tip, much appreciated

Regards
David E

related to the property


view. Click on the Text

Make sure that

in [EDITA1]. Notice

using msiexec, but with

david every

David
I think Sajan may have solved the problem, he suggested
putting [EDITA1] into the Edit1Value section as well as
havinf EDITA1 as the Edit1Property, and this has worked
by calling the command line as follows:

msiexec /i [msiname] EDITA1="something" ALLUSERS=2

by the way, EDITA1 still doesnt appear when using
WICLB.exe to view public properties ...

Regards
David E


list the public

on first use, so you

extra properties at the

properties.

Property table.

on the command-line


set by the control.

described) by

property. (Look up