>> Move the Image element to children of the Pages you want it to appear on. As
>> shipped, it's outside pages, so it always appears.
That sort of works; if I add the image to the Install page it displays on that
page but not on options but it still displays on Help. If I move the image to
the H
No, that's just another way of achieving what you're trying to do. See
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367852%28v=vs.85%29
.aspx
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 27 July 2012 15:12
To: 'General discussion for Windo
I've built a boostrapper installer with Burn v3.6.3109. The installer fails
with the following log. I find reference to a Burn bug in the list
archives, but emails in early January 2012 suggested the bug was close to
being fixed. Can anyone tell me the status of that issue (or if it's not
relevant)
Interestingly, if I don't codesign the bootstrapper (individual MSIs are *
not* signed), the installer succeeds.
On Fri, Jul 27, 2012 at 10:25 AM, Barry Wark wrote:
> I've built a boostrapper installer with Burn v3.6.3109. The installer
> fails with the following log. I find reference to a Burn b
I did that and it seems the location is getting changed but the EXE that I
am installing is still going to the default location. Do I need to call a
type 35 custom action for changing a registry value?
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 27 July
Generate a verbose log.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 27 July 2012 14:21
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Custom Action C++ Function / MsiSetProperty
Hi,
Yes thank you that solved the
Hi,
Yes thank you that solved the error and it is now installing without failing
however the exe I'm installing is not anywhere to be seen.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 27 July 2012 12:55
To: General discussion for Windows Installer XML t
You might need MsiSetTargetPath, as a directory property is slightly
different to a normal property. I'm not sure where you'd schedule it.
MsiSetTargetPath(hInstall, "INSTALLDIR", szLocalPath);
Assuming your directory layout looks something like this...
Also, don't f
No because I do not know what my customer has installed the main application
to. The DLL function checks all the possibilities and retrieves the correct
one, my function works perfectly. I just am struggling on how to retrieve
that variable and place it back into my MSI so that I can use it for my
Can't you do that with a RegistrySearch?
Neil
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 27 July 2012 11:47 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Custom Action C++ Function / MsiSetProperty
Hi,
Yes
Hi,
Thank you. I try minor upgrade with your recommends and it looks OK. Super :)
But downgrade with "install" mode is doing nothing. If i try "repair" mode, the
installation failed with this log:
[226C:1B80][2012-07-27T12:29:23]: Burn v3.6.2928.0, Windows v6.1 (Build 7601:
Service Pack 1), pa
Hi,
Yes that's exactly what I need to do.
Thanks
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 27 July 2012 11:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Action C++ Function / MsiSetProperty
What are you t
What are you trying to achieve ? Are you trying to install your MSI to a path
that is already stored in the registry ?
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 27 July 2012 11:30
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Actio
Hello,
Having some problems with my DLL custom action C++ function. I have the
function working properly it grasps the registry that I need to install to.
Somehow I need to extract the variable szLocalPath to my msi so that it can
then replace the install location. After research I think it's a
Hi,
The second time I recognize a strange problem. When I compile a bootstrapper
project on my PC the compiled executable is not really starting. The process
starts, but after that nothing happens, only the process stays in task manager.
The strange, an executable build from the same sources wi
15 matches
Mail list logo
