Thank you
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: mercredi 27 mai 2015 15:15
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] localisable msi packages in a bundle
I wonder if it is possible to chain from a MSI Package depending of
Hi Forum,
We are using WixUI_FeatureTree UI for our installer.
1. When i deselect 1 feature : Its respective Costing, Install Path and etc
UI Controls gets Disabled immediately.
2. When we deselect all the features : The Next button is still enabled and
allowing the installation.
Q1) Is
You should probably set a core feature to required:
Feature http://wixtoolset.org/documentation/manual/v3/xsd/wix/feature.html
@Absent=disallow
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX
By using the InstallCommand Parameter
ExePackage
Id=MyId
DisplayName=MyDisplayName
Cache=no
Compressed=no
PerMachine=yes
Permanent=yes
Vital=yes
Name=MySilentSetup
SourceFile=Setup.exe
Is patch 1.0.1 Uninstallable?
https://msdn.microsoft.com/en-us/library/aa372102%28v=vs.85%29.aspx
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
--
View this message in context:
I found some more information. The issue does not seem to be caused by NSIS
wrapper but by fact that original .exe name is different than what Burn
expects.
New STR are:
- Build BS as setup.exe
- Rename BS to installer.exe
- Run install from installer.exe
- Let .NET prereq be installed
- Reboot
I think I've encountered the reboot required scenario covered here
http://sourceforge.net/p/wix/bugs/3310/
Various windows services subsequently installed by our MSI fail as the
framework seems to need a reboot.
Having looked at what's done in \src\ext\NetFxExtension\wixlib\NetFx451.wxs I'm
Thanks for the suggestion .
For one product we have done exactly as you said. But for other product, we
have to have all the three features to be optional. So, user can deselect
any feature. But, if user does not select any, it is the problem.
1. Can't it be fixed from lower level?
2. how are
Thanks for your response.
if silent switch is not present in the command line of burn, I don't want to
pass /silent to the command line of the exe package. how to do that?
--
View this message in context:
This is just wrong. There are valid scenarios when Bootstrapper may need for
example to write a registry value. I don't say that it should be default
mode but it should be possible to request elevation for whole BS.
Burn is really powerful with custom MBA but this limitation just says We
know
There is a feature request for a RestartBoundary. Not implemented yet.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Martin Evans
Put the registry key in a package in the chain.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Jiri Tomek [mailto:katu...@volny.cz]
Sent: Friday, May 29, 2015 6:39 AM
To:
Sounds right.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Jiri Tomek [mailto:katu...@volny.cz]
Sent: Friday, May 29, 2015 5:19 AM
To: wix-users@lists.sourceforge.net
Hi Sampat,
WIX does not give you the functionality to disable the next button by default
if no feature is selected. But there are events conditions you can set to
disable the button.
This is what I do and works good for me:
--Publish a property on the CustomizeDialog page:
Publish
It's not fixed key. I use bootstrapper to gather various configuration
information from user which are then used to configure product and not all
of then are passed to MSIs. Adding logic to MSI to be able to get this
information via MSI properties, parse it and then store it in registry is
just
Thanks Pavan.
I will try your suggestion and get back with results.
Regards
Sampat
(Unisys, Blore, ktaka, India)
On May 29, 2015 10:46 PM, KONDURU Pavan [via Windows Installer XML (WiX)
toolset] ml-node+s687559n7600493...@n2.nabble.com wrote:
Hi Sampat,
WIX does not give you the
The BA should never modify machine state. What happens when your BA modifies
state during an update, but then the user aborts the update? If you modify
state, you have to restore it. You would also need to persist the rollback
info across reboot boundaries.
Windows Installer can be viewed
The Engine.Command.Display object lets you know if your BA is running with or
without a UI.
see src\burn\inc\IBootstrapperApplicaiton.h near line 17
see src\burn\engine\core.cpp near line 854
An example in a managed BA is at: src\Setup\WixBA\WixBA.cs Run Method.
One approach is to use the
Why custom actions to write registry keys? Why so much complexity? Actually,
those are rhetorical questions, I don't really want to know the answers.
smile/
You are choosing to work against installation best practices. Best of luck to
you.
19 matches
Mail list logo