Hi!
Thanks, that did the job ;). I've had the registry key in it's own
component, but moved it while looking into problem. Setting the guid to *
fixed the problem. Now I'm just not sure wheter I should set all my
component's guids to *...
--
View this message in context:
http://windows-installe
You've probably hit a bug. Can you open it? WiX v3.5 is still under
development, the IIS custom action is getting a lot of work.
On Fri, Jul 23, 2010 at 4:57 PM, Alex Henderson wrote:
> Hi All,
>
> We have an installer that was working fine under VS2008 - we just recently
> upgraded the installer
According to the log you posted, the InstallExecuteSequence was not run
because the install was canceled from WelcomeDlg (it returned IDCANCEL, not
IDOK). Try actually running the install to completion to see the example as
written.
Section 3.3 introduces the sample. Section 3.4 (not in the code y
On 7/25/2010 8:10 AM, Lukas Haase wrote:
> However, there is also need to replace Product/@Id and
> Product/@UpgradeCode ...
Use preprocessor variables and/or localization variables.
--
sig://boB
http://joyofsetup.com/
--
On 7/25/2010 8:00 AM, Lukas Haase wrote:
> Maybe this is wrong and InstallExecuteSequence is /not/ called when
> running in full/reduced UI mode?
>
It is called but after the UI, if any. If you want to call a custom
action with user input from a dialog, use a DoAction control event.
--
sig:
On 7/20/2010 3:06 AM, Neil Sleightholm wrote:
> Yes I tried that too, although it looks like it is loading the correct
> file (i.e. the FullPath is correct in the properties) it still sets the
> extension to -ext WixFirewallExtension.dll which candle the tries to
> load from the bin folder.
>
If the other setup package is ultimately MSI, you should ideally use the
Upgrade table to remove it (via the RemoveExistingProducts action using the
"Major Upgrade" method). However, that doesn't work if the ALLUSERS value
differs between the two installations and you will need to look at ways to
b
Even embedded UI can be turned off/disabled on any given computer.
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Sent: Saturday, July 24, 2010 5:56 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Questions about showing warning/error message
dialog
Thank
Dear Blair,
Thank you for the hint! I will replace my MessageBox-call prompt with
MsiProcessMessage/WcaProcessMessage ...
Apart from this, my approach is good practice? Or is it maybe better to
pass the uninstall to MSI and executing it there rather than calling
ShellExecuteEx from the DLL?
R
Dear Rob,
Thank you for your reply.
Am 23.07.2010 08:01, schrieb Rob Mensching:
> 1. You can have multiple .wxs files to create a single or set of MSI files.
> I recommend breaking your product down into useful chunks and putting them
> in Fragments then grouping the Fragments in logical files. M
Hi all,
I have downloaded and tried the Sample CA from the tutorial [1]: [2]
I compiled the DLL, ran candle/light and started the SampleCA.msi:
msiexec /i SampleCA.msi /l*xv SampleCA.log
This is the resulting SampleCA.log:
http://pastebin.com/Zph9xk5T
As you can see the neither the word "Chec
11 matches
Mail list logo
