Probably. I trust start more than cmd to not mess with the ERRORLEVEL, that's
all.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Shane Corbin [mailto:shane_cor..
Fair enough. I suppose you could do this too:
cmd /c bundle.exe /quiet
Thanks Rob.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-ERRORLEVEL-from-Bundle-installed-with-quiet-tp7593895p7593897.html
Sent from the wix-users mailing list
start /wait bundle.exe
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Shane Corbin [mailto:shane_cor...@selinc.com]
Sent: Tuesday, April 1, 2014 11:47 AM
To: wix-
When I run my bundle from the command line it returns immediately with a
return code of zero. How do I run the bundle silently/quietly and retrieve
the return code to determine if it succeeded or failed?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble
Yes, there is a tremendous amount of trust between a Bundle and it's payloads.
The Bundle knows a lot about its payloads and does quite a bit to make sure bad
guys don't slip bad stuff in there to usurp your customers. It does mean that
changes to 1 or more payloads typically means updating the
On 01-Apr-14 08:32, Pally Sandher wrote:
> Anyone seen this before? I've bundles built using WiX v3.6 which are failing
> to apply a patch which has been signed by a renewed code signing certificate.
> The bundle was signed by the previous certificate which expired last month
> but both the bund
So I rebuilt the bundle without changing any of the code, simply supplying the
newly signed patch at the path specified in my bundle's .wxs file (all other
payloads were also as before).
Guess what, it installs perfectly fine now. No need for anything like the
System Update Readiness tool or Sy
Customers may vary.
My customers are not computer inclined at all and 90% of time don't have IT
backup. They are mechanical technicians who often who don't know the first
thing about computers. If the installer doesn't work they can't do their job.
The PC is an annoying tool they have to use
In this case the code is valid, as Windows Update uses the MSI
Installer as the main method of distribution, so I tend to disagree in
this case.
Carter
Quoting Pally Sandher :
> BRB, doing that on every machine across the planet.
>
> This just in, WiX error codes != Microsoft error codes.
>
BRB, doing that on every machine across the planet.
This just in, WiX error codes != Microsoft error codes.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Sol
I'll give that a try but it doesn't help for existing Bundles & I don't
particularly want to rebuild dozens of released Bundles just to fix this.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate wit
I apologize for cludging up the list with possible unneeded replies,
but it's things like this that get me riled up. As an IT Professional
and programmer, it really bothers me when as programmers, we ignore a
xritival erroor bevause we know the option to do so. I'm a proponent
of a health
Yes the machines have internet access. The file is pulled from a URL as you can
see in the 2nd line of the log.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental
I suggest doing this only after running the System Update Readiness
Tool as I stated earlier. Although it has been my observation that
Method 2 only makes the issue worse...
If the System Update Readiness Tool reports no inconsistencies, then I
would feel more comfortable suppressing the wa
Also See this KB article:
http://support.microsoft.com/kb/958044
Carter
Quoting Wesley Manning :
> I should mention there was discussion by wix team on defaulting to
> hash checking of files instead of the vericode signature. I changed
> over my bundles to use hash checking. From what I c
I noticed a problem once. Not sure why. I also saw comments from others
that this can be problematic, so I set SuppressSignatureVerification="yes"
on my packages in the bundle chain.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-fails-to
I should mention there was discussion by wix team on defaulting to hash
checking of files instead of the vericode signature. I changed over my bundles
to use hash checking. From what I can tell and find using hash verification is
just as good.
-Original Message-
From: Wesley Manni
Does the computer have internet access? Looks like it's not finding a "parent"
certificate for validation. Not sure. Others on this list said that
validation can be a problem when you don't have internet access and the proper
certificates aren't on the computer.
-Original Message-
Anyone seen this before? I've bundles built using WiX v3.6 which are failing to
apply a patch which has been signed by a renewed code signing certificate. The
bundle was signed by the previous certificate which expired last month but both
the bundle & the patch show up as valid signatures when I
Hello,
I have been busy trying to set up a bootstrapper to work with multiple instance
transforms.
Does burn work with this in WiX 3.8?
Maybe there're alternatives?
--
___
WiX
I mixed MSIENFORCEUPGRADECOMPONENTRULES with
MSIUNINSTALLSUPERSEDEDCOMPONENTS
So if i use MSIENFORCEUPGRADECOMPONENTRULES="1" then the patch will fail
because of the violation of the rules, which is good but still a little bit
late in the process to catch it.
MSIUNINSTALLSUPERSEDEDCOMPONENTS does
I tried MSIENFORCEUPGRADECOMPONENTRULES briefly without success but i'm
going to try it more.
However, InstallShield seems to detect these problems for example:
ISDEV : error Val0001: The file 'readme.txt' with a target of
'[programfiles64folder]\a\readme.txt' appears to have been removed from th
Hello,
I'm just new to WiX and maybe, my question don't make sense, this might be
because I'm not an English native speaker.
So here my question:
I'll like to patch / hotfix an application that was installed by an
Bootstrapper Application.
One more question, is it enough to simply increment th
Hi,
I am using Wix 3.8. I have created a web installer which downloads and
install the MSI packages. MSI packages are getting downloaded and placed in
%ProgramData% or %LocalAppData% based on the ForcePerMachine attribute in
MSI Package element by default. Bootstrapper log files are created under
24 matches
Mail list logo
