1. No, not generally a good practice.
On Fri, Oct 4, 2013 at 11:45 PM, Fyodor Koryazhkin wrote:
> Hi All,
> I would like to hear an opinion from users and administrators about the
> following issue:
> Recently I was asked to change during installation MSDTC service
> configuration, namely Failur
My problem is that my Burn setup is very very slow, compared with the old
Installshield setup.
For this reason I have reported very bad feedback by users.
As the verbose logging for the msi is very big more than 100 MB, I have
supposed that one of the problem was the writing of the verbose log.
Having the below feature structure, and running the MSI with the following
command line
msiexec /I SmallSetup.msi /norestart /Lv c:\BA\install.log ADDLOCAL=FeatureB
INSTALLFOLDER=c:\batom
I would expect to see both Feature and FeatureB1 selected...to my surprise
only FeatureB is selected
even i
Yeah, read the fine print about ADDLOCAL. If you set it, you take full
control of the feature tree.
On Sat, Oct 5, 2013 at 5:00 AM, tom wrote:
>
> Having the below feature structure, and running the MSI with the following
> command line
>
> msiexec /I SmallSetup.msi /norestart /Lv c:\BA\install
Thanks...i read it least 50 times :) , do you have an idea how to better
support (at least)
ADDLOCAL and REMOVE in MBA?
Attributes:
"The remote execution option for features that are not installed and for
which no feature state request is made by using any of the following
properties"
ADDLOC
What is more conusing me is that when i also set
msidbFeatureAttributesUIDisallow
On B1 it will install B1 as wellbut the documentation says this
attribute meant for controlling for the UI.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ins
did you add reference to WixBalExtension?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unresolved-reference-to-symbol-WixBootstrapperApplication-ManagedBootstrapperApplicationHost-tp7589453p7589473.html
Sent from the wix-users mailing list ar
It often helps to actually look at the log to see if there are times when
an install is slow. Some possibilities:
1. InstallValidate actions may be slow because of the number of
files/components.
2. Self-registration of COM Dlls slows installs down because every Dll and
its dependency needs loadi
As Rob says, if you do a (often silent) install using ADDLOCAL or REMOVE
you take full control of the feature selection, which means that every
feature needs a specification for ADDLOCAL or REMOVE, not just some you
have a special interest in. Doing this also sets the Preselected
property, so the C
I think you said the situation involved limited users, and they probably do
not have the right to reboot the system, so Windows will not ask for
permission - it'll just do the reboot, even if it's a ScheduleReboot that
could ask. A user with shutdown privilege would get shown the dialog asking
whet
if a child feature has both msidbFeatureAttributesUIDisallow and
msidbFeatureAttributesFollowParent
And even that only its parent was specified in the ADDLOCAL then the child
feature will be installed
I just checked it in MSI
I know it is not BA related. I am just trying to provide support for
If you want your BA to control feature states, set the
MsiPackage/@EnableFeatureSelection and handle the feature state planning
callbacks.
On Sat, Oct 5, 2013 at 11:06 AM, tom wrote:
>
> if a child feature has both msidbFeatureAttributesUIDisallow and
> msidbFeatureAttributesFollowParent
>
> A
I already do iti have acomponent which parse addlocal and remove
and in the callback set the feature state
Tomer Dror
Intergraph Corporation.
Intergraph Israel.
P: +972 (4) 8779191-1222
Skype:tomer.dee
http://www.intergraph.com
.
From: Rob Mensc
Hi,
I'm just in the process of breaking out an installer in to multiple smaller
installers.
I'd also like to have an auto-updating capability.
If I break components of the application in to their own installers and wrap
them in an executable (bundle) can I then update the individual msi files? O
Hi,
You can update the individual msi files using minor updates (MSP). This does
not have impact on the bundles uninstall/repair behavior.
For major updates you should update the bundle. (Although it is possible to
do a major update on the MSI directly) If you perform an major update on a
msi, th
Hi,
Thanks for confirming what I suspected.
Regards
Sean.
-Original Message-
From: Markus Wehrle [mailto:mar...@laika42.com]
Sent: 06 October 2013 00:43
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] queries regarding update deployment
Hi,
You can
Right, sorry, I forgot that all translates down to ADDLOCAL and friends in
the end (since that is the only way to control features from the outside),
Heh, this is why the documentation in the wix.chm says: "Managing feature
selection requires special care to ensure the install, modify, update and
Heat also puts one file per Component. That can slow things significantly.
Optimizing the order of the files being installed for speed as well as size
(we try to do stuff to optimize for size over speed in WiX v3.x) is going
to be (hopefully) fixed in WiX v4.
On Sat, Oct 5, 2013 at 10:24 AM, Phi
18 matches
Mail list logo
