I don't think burn currently supports this kind of scenario well (it may but
I am not an expert).
What you could do is make a per-user burn bundle that just installs your msi
silently then add that as an .exe package to your main with-prerequisites
bundle.
Or indeed leave it the way you have it a
Hi there,
I have an installer which installs a service with user credentials it
receives from the user. On an upgrade I don't want to remove and reinstall
the service because this results in loosing the credentials. When the user
uninstalls the application I do want the service to be uninstalled.
I know all the product IDs, and the UpgradeCode of course, and from what I
understood of the bootstrapper, it's also got the problem you're describing
that it doesn't work if it was installed by a different user. Since we've got
an automated installation platform that sends new software to the c
Sound like a workable solution.
-Original Message-
From: Tom - [mailto:mittegetm...@hotmail.com]
Sent: 30 July 2013 11:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Remove Existing Products - Not Happening
I know all the product IDs, and the Upgrad
Cheers, I'm going to go for this. Is there any way in my installer to do what
FindRelatedProducts according to the install-log did: confirm that there is an
installation on the computer already by using the old UpgradeGrade, in spite of
which context it's installed, and stop the installation wit
I don't think it is possible to check if another user install the application.
Maybe you could check for a known file that all users can see.
-Original Message-
From: Tom - [mailto:mittegetm...@hotmail.com]
Sent: 30 July 2013 12:46
To: General discussion for Windows Installer XML toolset
Is this a Windows Service? More than like, if you don't shutdown the service,
the attempt to update one or more of the binaries will fail or force a reboot.
Unlike OS/2, Windows does not have an API to unload DLL's or executables.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack
I don't mind stopping and starting the service. Just not reinstalling it.
Shay.
On Tue, Jul 30, 2013 at 3:56 PM, John Cooper wrote:
> Is this a Windows Service? More than like, if you don't shutdown the
> service, the attempt to update one or more of the binaries will fail or
> force a reb
Well in that case, what is your upgrade scheduling? You can probably get the
effect you want with appropriate scheduling in the MajorUpgrade element.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
What do you mean by upgrade scheduling?
Thanks!
On Tue, Jul 30, 2013 at 4:24 PM, John Cooper wrote:
> Well in that case, what is your upgrade scheduling? You can probably get
> the effect you want with appropriate scheduling in the MajorUpgrade element.
>
> --
> John Merryweather Cooper
> B
Wix Documentation -> Wix Schema References -> Wix Schema -> MajorUpgrade
Element. You are particularly going to be interested in the values the
Schedule attribute can take. The default is "afterInstallValidate". It sounds
like you really want an "on top of" upgrade which would use
"afterInst
Classification: Public
The 5 merge modules have of about 10
wixlibs The files in the MergeModules and WixLibs are built as AnyCPU however
since I need to install the services for 64 bit OS and 32 bit OS I need two
MSI's one for 32 and one for 64 bit
So I am not using any binary files that are
Hello,
I'm Installing a driver with DPInst and I need to ckeck the installation
after.
I'm using this custom action:
I know that only the value = '0' is considered success for the custom
action, but the DPinst don't return 0 when the installation was successul.
What can I do to change the behav
Using the link you'd provided earlier, the bootstrapper-example in it had some
interop going with the MSI, and it included a call to GetRelatedProducts with
the UpgradeCode. This returns GUIDs, if installed, that you can use to further
via Interop query whether it's installer for all users, what
Look in the Bundle's log file. It'll show what was installed. If anything
per-machine was installed, it will have to elevate.
On Tue, Jul 30, 2013 at 1:14 AM, David Watson wrote:
> I don't think burn currently supports this kind of scenario well (it may
> but
> I am not an expert).
>
> What you
Good afternoon,
>From my previous problems, I pieced together a bootstrapper that should do
>nothing but uninstall a non-WiX installation of a program. I don't need the
>bootstrapper UI. I wouldn't mind it, I guess, had it looked the slightest like
>the other UI:s in WiX and Windows, but now I
Good afternoon,
I've got a series of custom actions that can each present reason for a failed
installation. I am currently getting "the installation completed/failed
prematurely" or what it says when something fails. I like that screen, but I
would like to show my own text for why it failed: S
It can be UI-less if your BA doesn't show UI.
On Tue, Jul 30, 2013 at 8:00 AM, Tom - wrote:
> Good afternoon,
>
> >From my previous problems, I pieced together a bootstrapper that should
> do nothing but uninstall a non-WiX installation of a program. I don't need
> the bootstrapper UI. I wouldn
Assign them to a feature and condition the feature.
Dave
- Original Message -
From: Steven Ogilvie
To: General discussion for Windows Installer XML toolset.
Cc:
Sent: Tuesday, July 30, 2013 7:16 AM
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in
Prod
No, you probably need to:
1) log a message;
2) display an error dialog;
3) display some action text;
It's not really a function of the particular UI you're choosing since any
dialog boxes you're going to pop are going to display because of spawning and
not scheduling.
But it isn't going to hap
Classification: Public
Damnit, I didn't think of that... I will try that thanks!
-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: July-30-13 11:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a co
I get a 503 when I attempt to browse to wixtoolset.org, is it down for
maintenance?
--
Tony
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caugh
+1
-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: Tuesday, July 30, 2013 11:36
To: WiX Users
Subject: [WiX-users] wixtoolset.org down?
I get a 503 when I attempt to browse to wixtoolset.org, is it down for
maintenance?
--
Tony
--
Classification: Public
Sigh same merge modules just compiled under x86 and x64
Get the error:
Error 49 The merge module 'EnterpriseServicesMM_x64' contains a file
identifier,
'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8E92',
that is duplicated either in another
Should be back now. AppPool was dead, I'll ask why.
On Tue, Jul 30, 2013 at 8:42 AM, Alain Forget wrote:
> +1
>
> -Original Message-
> From: Tony [mailto:yellowjacketl...@gmail.com]
> Sent: Tuesday, July 30, 2013 11:36
> To: WiX Users
> Subject: [WiX-users] wixtoolset.org down?
>
> I ge
I am also getting a HTTP Error 503.
*John*
On Tue, Jul 30, 2013 at 9:35 AM, Tony wrote:
> I get a 503 when I attempt to browse to wixtoolset.org, is it down for
> maintenance?
>
> --
> Tony
>
> --
> Get your SQL databa
Confirmed, it's up.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, July 30, 2013 11:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixtoolset.org down?
Should be back now. AppPool was dead, I'll ask why.
On Tu
Isn't the win64 setting on the component so you need to build a 64bit and a
32 bit version of each merge module (or wixlib).
This is easily done with a shared .wxs file and a compilation setting.
I have 32 and 64 bit components all up my build tree just because one package
needs a 32 and a 64 bit
If you do it that way, you'll need to condition the affected components too or
there will be some edge cases where the feature might not install but the
components still will.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Off
Classification: Public
Yup I have the configuration set in the Solution file for my Services Solution,
and in each MergeModule WIXProj I have set up x86/x64 configurations so it is
built twice once for x86 and once for x64 and placed in different folders
wixlib/wixlibx64 (both merge modules and
Thank you! It turns out that "session.Message(InstallMessage.Error, record);"
was sufficient enough for my needs, as it displays a messagebox with a bit an
error text of my choosing -- will make users more understanding of the "ended
prematurely"-message.
Best Regards,
Tom
> From: jocoo...
Thanks.
On Tue, Jul 30, 2013 at 12:03 PM, Alain Forget wrote:
> Confirmed, it's up.
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Tuesday, July 30, 2013 11:53
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] wix
I'm trying to create a managed burn bootstrapper to install a MSI as either
per-user or per-machine. My bootstrapper will pass in a different ALLUSERS
value to the MSI depending on the choice of the user. I'm currently testing on
a Windows 7 machine as an administrator, UAC is turned on (defau
You lose several of the benefits of bundles by setting DisableRemove. Rob
listed the effects if DisableRemove is NOT set.
> From: tomas.k...@cellavision.se
> To: wix-users@lists.sourceforge.net
> Date: Fri, 26 Jul 2013 12:01:13 +
> Subject: Re: [WiX-users] [wix-users] Impact of installed bur
You can use the MajorUpgrade element (use the UpgradeCode you prefer in your
Product element) and use just the offending UpgradeCode in the Upgrade element
(to find/remove versions using it).
> From: jacob.hoo...@greenheck.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 29 Jul 2013 17:57
Just to clarify:
If you implement this pattern (BTW: heat uses this pattern by default):
...
...
...
And then in your patch you reference Comp2 you will only patch Comp2 (Comp1 and
Comp3 will be excluded from the patch).
If i
You need one set of merge modules for x64 and another for x86, correct?
Use conditional compilation. You don't need all the merge modules in the x86,
correct? Why put them there?
Or am I missing something?
> From: steven.ogil...@titus.com
> To: wix-users@lists.sourceforge.net; d...@agilityre
Oh, the joys of SelfReg.
Is using the DIFxApp WiX extension an option to allow you to avoid SelfReg
techniques?
DPInst is not recommended for use in MSIs (DIFxApp is supported in MSIs as
employed using the WiX extension).
If you absolutely cannot use DIFxApp and you must use DPInst then you
I assume you employed the technique from the tutorial
(http://wix.tramontana.co.hu/tutorial/localization/tfel-ot-thgir) since
WixUI_RTL_InstallDir isn't in the toolset-supplied UI extension.
It's possible there's a bug in the tool that creates the RTL files. Personally
I think there's a bug th
39 matches
Mail list logo
