On 6/15/2014 3:30 PM, Tunney, Stephen wrote:
> Think I have time to squeeze this in for 3.9?
Depends on the scope of the fix. Deadline for low-bar changes was 6-June.
--
sig://boB
http://joyofsetup.com/
--
Open source b
On 6/20/2014 1:24 PM, Kyle Corsi wrote:
> Error:
> light.exe : error LGHT0001 : Item has already been added. Key in dictionary:
> 're
> g73E8E70EB9CA78EDD5C4CA9264E4E34F' Key being added:
> 'reg73E8E70EB9CA78EDD5C4CA9
> 264E4E34F'
Which version of WiX are you using?
--
sig://boB
http://joyofse
On 6/23/2014 5:17 PM, George Fleming wrote:
> 1. In element, the "Id" attribute is different,
> auto-generated GUID is used each time we patch.
That means you're not using WiX to build the patches but a tool like
MsiMsp. Nothing WiX can do to change the outcome. That's why pure-WiX
patching wa
On 6/23/2014 4:50 AM, Anton Iermolenko wrote:
> [14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
> registration on package: PrerequisitesMsi, bundle scope: PerUser, package
> scope: PerMachine
Is this intentional? You might want to make both packages per-machine.
> [14A0:14D8]
Hi Wix guys,
Please help.
I have a bundle, which contains a ExePackage, call it Bundle1
http://schemas.microsoft.com/wix/2006/wi";>
Now I have a minor upgrade for other package and I update the authoring a bit
and get Bundle2:
http://schemas.microsoft.com/wix/20
I have been working on a similar problem today, with same error.
[14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
all files from container, erf: 1:4:0
In my case the problem was induced by changes that I made to my mba, so the
problem was not intermittent. In my case I
Sorry, due to legal reasons, I cannot really post my Patch wxs file. But it's
basically the same file used in both patches. The only difference between
patches are:
1. In element, the "Id" attribute is different, auto-generated
GUID is used each time we patch.
2. In element, the "Sequence
I have:
(both ui/exec sequences)
SAMEVERSIONDETECTED
(this is the same stuff I've been using since wix 3.0)
Dave
>
> From: Steve-Ogilvie
>To: wix-users@lists.sourceforge.net
>Sent: Monday, June 23, 2014 1:39 PM
>Subject: Re: [WiX-us
I tried with
NOT SAMEFOUND OR Installed
But if product version was changed in first 3 digits it still said the above
message
Any idea what I did wrong?
steve
From: Rob Mensching-7 [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7595422...@n2.nabble.com]
Sent: June-23-14 4:
The 4th digit is recognized in the Burn Engine but not in the MSI
Product.wxs. You must manually write an install condition to check
the 4th version number, or use the same product code with an Upgrade
condition, ie:
If 14.4.6.7 is installed, perform an upgrade install of 14.4.6.8, that
w
It's possible using Upgrade element.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Monday, June 23, 2014 12
Seems like a reasonable thing to open a bug against Insignia to handle better,
if possible.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Peter Prikryl [mailto:p
Our productcodes change build to build (that way when we release a new version
the productcode is different, so the new release is an upgrade)
So there is no way in WIX with different productcode/same version (diff 4th
digit to recognize same version install?)
Thanks,
Steve
From: eyoung100 [v
Set the ProductCodes to the same value as 14.4.6.7 in both situations
Carter
Quoting Steve-Ogilvie :
> Hi folks,
>
> I have 2 questions... (Using WIX 3.8)
>
> 1. MSI
> I would like to stop build to build installs (bring up warning?)
> i.e. i have 14.4.6.7 installed, then I run today's build whi
Ok, I found out that there was an error in the build script - the signing
process was being executed twice. The insignia does not handle the
extraction of already signed engine well and the behavior is the result of
it.
After removing the certificate from the extracted engine.exe, the values in
th
Hi folks,
I have 2 questions... (Using WIX 3.8)
1. MSI
I would like to stop build to build installs (bring up warning?)
i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8
(the product code is different, the upgrade code is the same) this is my
upgrade element:
the .8 v
Argh, I apologize, It looks like I was checking the wrong log. Running as
admin on the VM spits out similar logs as my machine for elevation. It still
won't run on any Win7 machine other than mine, but all the Win8's work just
fine. Any ideas as to what would be missing? That debugger you linked wa
I spent sometime digging into this using the debugger but I can't seem to
find anything errors. I was digging into the logs for the installs on my
machine, the VM and the other win 7 user machines. All the failed installs
look like this:
[0778:055C][2014-06-23T10:22:04]i000: Loading managed bootst
There are a couple issues, but You'd need to test them to be certain:
1. 56 MB may be too big to handle efficiently, although I've seen
posts from fellow readers with filesizes in the 500MB range. To test
this, replace your actual package with a text file. If the Text File
installs, we nee
Setup.exe is 56Mb. So there error is not Wix Boostrapper specific you mean
and instead OS specific? Could it be domain permission issues?
On Mon, Jun 23, 2014 at 5:15 PM, Carter Young wrote:
> How big is the file?? Regardless the error number you indicate only
> show the types of errors I put
How big is the file?? Regardless the error number you indicate only
show the types of errors I put in the list as I googled...
Quoting Anton Iermolenko :
> Not sure this is the case here. It's not bad RAM or corrupt file, since
> once file is copied to user's desktop folder the installation su
Not sure this is the case here. It's not bad RAM or corrupt file, since
once file is copied to user's desktop folder the installation succeeds.
Any other ideas?
On Mon, Jun 23, 2014 at 4:22 PM, Carter Young wrote:
> Some Possibilities:
> 1.
>
> http://www.sevenforums.com/installation-setup/347
Some Possibilities:
1.
http://www.sevenforums.com/installation-setup/34736-0x80070570-error-code-install-one-easy-solution.html
2. https://answers.yahoo.com/question/index?qid=20091231164201AA1jCpl
3.
http://superuser.com/questions/432368/installation-error-0x80070570-while-installing-windows-7
That sounds like a permissions problem to me. Check your windows-based ACLs
for all files and folders involved in your process. Did you install WIX from a
Cygwin command line?
-Original Message-
From: eric [mailto:eric.bu...@lmco.com]
Sent: June-23-14 9:06 AM
To: wix-users@lists.sourc
It does, indeed.
I realized that it runs fine in Cygwin, but not from the Windows
commandline. Any idea why that might be? I would prefer not to have to set
up Cygwin on our build server.
scubasteve2 wrote
> Does "./MyFolder" exist?
--
View this message in context:
http://windows-install
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's desktop and
run it from there. Any ideas what stands behind "0x80070570" error?
Previously, we used to deploy to our clients using single MSI and had no
such issues,
I have found the issue myself. Following code works perfect.
Thanks a lot.
> From: c...@live.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 23 Jun 2014 08:14:27 +
> Subject: Re: [WiX-users] Unable to uninstall previously installed product
>
> Hi,
> I have tried and it seems that it wi
Hi,
I have tried and it seems that it will work if I can pass the following trouble.
I get the uninstallstring using:
This returns me: C:\Program Files (x86)\MyApplication\
Then I have a custom action to run the uninstaller string.
REGISTRYFOROLDINSTALLER
I got the follow
28 matches
Mail list logo
