Also you could have 2 different components - one for each service type - with
opposite conditions. It'll be easier to maintain if the 2 versions of the
files differ further as time goes on.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 20 October 2012 18:43
T
Thanks Rob, unfortunately I cannot find any information about
the OnPackagePlan callbacks online nor can I see it used in the WixBA
source code. Could you point me in the right direction?
Thanks!
On Fri, Oct 19, 2012 at 6:59 PM, Rob Mensching wrote:
> Check on the OnPackagePlan callbacks.
>
> O
Official docs here
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372855%28v=vs.85%29
.aspx
After that, you will find my colleague's blog article useful
http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/
and search this mailing list at nabble.com wh
Yes, you'r right REINSTALLMODE is set to "amus" by an earlier developer.
I have to figure out why it's done and if I can change to "omus".
I believe the REINSTALLMODE also affect all the mergemodules as well?
Oivind
--
View this message in context:
http://windows-installer-xml-wix-toolset.687
> -Original Message-
> From: Igor Brejc [mailto:igor.br...@gmail.com]
> Sent: 20. oktober 2012 20:04
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Getting started writing a custom Bootstrapper
> interface
>
> Hi,
>
> Some more pointers from me. I'v
Sourceforge cooperated with me now, so I filed a feature request:
https://sourceforge.net/p/wix/feature-requests/709/
Daniel E. Bruce
> -Original Message-
> From: Daniel Bruce [mailto:daniel.br...@prediktor.no]
> Sent: 22. oktober 2012 13:00
> To: General discussion for Windows Installer
I really need help on this...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-to-inetpub-wwwroot-tp7581451p7581511.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi all
I've started the arduous process of recreating a new installer using WiX to
replace our existing VS2010 Setup Projects.
Unfortunately it's not been smooth sailing, because to be able to create some
basic installation capabilities like dependencies discovery, website
installation, conten
decided to use two components that modify the .config file and condition it
one if a Server install the other if a Client install...
Thanks Rob and Peter for your input :)
Cheers,
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Conditional
Retrying this as the last attempt bounced..
If you are using heat you could provide it with a -t and an XSLT transform
which would be used to tweak the default output to your liking. This would
allow you to only have the need for the generated file.
Jacob
-Original Message-
From: Joha
Hi all,
I've been successfully using WiX for a long time now and I'm very happy with
it. Many thanks for all the effort you are putting into this project.
Currently I'm using WiX together with a standard Visual Studio bootstrapper
for .NET and other prerequisites. I want to replace this with Burn
figured it out... saw a build warning about a property I created with another
property as part of the path, you have to create a custom action to do that:
NOT Installed
Sigh it pays to look at warnings...
--
View this message in context:
http://windows-installer-xml-wix-toolset.68755
Hello,
what is the strategy if a 3rd-party Merge Module does not install
correctly?With 3rd-party I mean, I have the files of the Merge Module, only the
msm file.
In my case, if I put the msm in a VS-Installer made msi, it works.If it is in a
WIX made msi, some dll ( COM ) are not registered ri
Usually, the issue is that the Merge Modules do not have all the necessary
actions to correctly install themselves (which is incorrect to the spec).
If you're missing actions, you can add them to your package by just adding
the action name, like:
and you're package will have what the Merge M
I've got an installer that is working, with the exception of making start
menu shortcuts. I've done this before in wix 3.5, but now I keep getting
the following error:
The installer has insufficient privileges to access this directory:
C:\Program Files (x86)\MyApp. The installation cannot continu
What I do in this scenario is scan the logs to find out what files are in use
and causing the reboot - look for a return code of 3010 from one of your MSIs -
burn will only do a reboot if one of the packages (MSI or EXE) requests it.
Once you know that you can decide how to handle it more effect
16 matches
Mail list logo
