Hi there, I'm experiencing a strange issue and was wondering if anyone had
some insight into it.
I have an installer package where all the components are 32-bit, but I must
nonetheless interact with 64-bit prerequisite software and install on a 64
bit platform.
Now, all I am trying to do at this
Hi there,
I'm trying to create an installer package that writes a default value on a
fresh install but preserves a changed value on upgrade or maintenance.
What I did was author my MSI package in the following way:
In the resulting package, the relevant entry in the Property ta
Hi there,
I'm trying to create an installer package that writes a default value on a
fresh install but preserves a changed value on upgrade or maintenance.
What I did was author my MSI package in the following way:
In the resulting package, the relevant entry in the Property ta
/upgrade?
:D
On 5/25/07, Rob Mensching <[EMAIL PROTECTED]> wrote:
Unfortunately, by design. That's the Windows Installer behavior for
RegSearch. The MSI SDK will have more details if you desire.
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *BES Installer
*Se
I'm seeing the same behaviour.
In my component I have the following lines:
In the resulting package, the relevant line in the Property table is:
Property = PORTVALUE, Value="1234"
In the Registry table, Value = #[PORTVALUE].
When I run this on a fresh install, it correctly wr
5 matches
Mail list logo