Hey, According to the log file the files are skipped because of the
Modification Date, I'm currently doing a test using the 'version lying' with
the DefaultVersion set. I'll let u guys know how it goes.
Thanks :P
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: 29 Octo
Hey Phil, I'm all for the best route on getting all the files replaced, I have
no idea how the file hashing works?
Christoffel le Roux
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 29 October 2013 05:24 PM
To: General discussion about the WiX toolset.
Subject
I look at version lying as a necessary evil to subvert Windows Installer's
insufficient costing story. There are ways of reducing the repair risk to
zero.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 29 October 2013 05:24 PM
To: General discussion about the
Ok, figured out what was wrong, operator error . I had my Upgrade and Target
sourcefiles reversed. After I fixed that it worked as expected
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Creation-Properties-example-in-manual-not-working-
On wixtoolset.org there is a link to a book on wix. I recommend that and the
tutorial at wix.tramontana.co.hu.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: October-29-13 6:36 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Fwd
Any ideas why this happens (sometimes) only when using WiX during the build
process?
http://stackoverflow.com/questions/14879411/wix-ice-validation-errors
I have it happen (occasionally) in my local VS2012 builds. Often a rebuild
and/or a clean-rebuild on the WiX solution will get me a good buil
I would like to know if Burn could handle the following scenario.
Consider the old pre-burn WiX single MSI distribution. Now consider the
way it is today with small micropackges for wix, votive, sdk and son on.
Now imagine the sum of those packages 1GB are call it the Big product.
Let
ICE38:
http://stackoverflow.com/questions/12860316/ice38-component-installs-to-user-profile-error-for-a-specific-component
ICE64:
http://stackoverflow.com/questions/4627861/wix-the-directory-is-in-the-user-profile-but-is-not-listed-in-the-removefile-tab
ICE91:
http://stackoverflow.com/quest
A tester ran into an issue recently where the the machine got a BSOD near the
end of an install. While there is not a problem with the install itself,
the blue screen caused a strange side effect that I want to explain.
The install log indicates the install was successful and product is on disk
a
That information is written out by the standard actions PublishComponents,
PublishFeatures and PublishComponents actions.
If this is reproducible, adding ! to the logging ( /l*v! ) instructs MSI
to log each line immediately and can be useful in not "missing" any
useful logging information t
On 9/25/2013 2:47 PM, keith.doug...@statcan.gc.ca wrote:
> Hi everyone, I thought I'd update the answer to my question from last week:
>
> For what it is worth, our server support team found KB931125, which seems to
> have been the correct one for Server 2003 R2 Enterprise.
By the way don't insta
If the issue is the modification date different from the creation date,
make them the same with an early custom action. The reverse of this :)
http://blogs.msdn.com/b/astebner/archive/2013/05/23/10421023.aspx
Phil Wilson
On Wed, Oct 30, 2013 at 4:34 AM, Christopher Painter wrote:
> I look at v
I am currently testing the creation of WiX patches using Patch Creation
Properties. Now I am trying this over Pure WiX patches because the versions
that we will initially be patching have already been released and when they
were built they were NOT built to generate the .wixpdb files. So we have to
I guess I could disable those three ICE validators as they always seem to
be the ones that blow-up with the "ICE Internal Error 1002. API Returned:
1615 " error message.
I was just wondering what is it about WiX build tasks/actions and/or the
ICE validators that causes MSBUID to "sometimes" blow-u
And a rollback CA and a commit CA and. :)If that works for you,
fine. I won't call it a 'bad thing'.We all have to do dirty things now
and then, don't we? :)
My personal favoring is setting the installdir to C:\Progra~1\ grin.
From:
See here:
http://connect.microsoft.com/VisualStudio/feedback/details/731094/ghost-msbuild-exe-in-vs11-when-using-custom-task
Sounds like you may need a Service Pack
Quoting Tony :
> I guess I could disable those three ICE validators as they always seem to
> be the ones that blow-up with the "I
Yes. Two options one does as you describe, the other maybe less so (but might
work better):
1. Bundle v1.1 is an upgrade of v1.0. Bundle v1.1 will need to know about the
other 19 packages but you don't have to ship them. Burn will skip all the stuff
that is already present on the machine. Howev
2013/10/30 Christopher Painter :
> One approach would be that 1.1 is a web download installer that contains
> all 25 packages but will only download 5 of them. I'm not sure if "Big"
> product will buy into this or not though.
As far as I know, shipping packages in the bundle vs downloading them
Thanks. I can add this to the bug report for the tester to try.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-does-Windows-Installer-write-install-information-to-the-registry-tp7590115p7590125.html
Sent from the wix-users mailing list archi
I like this idea. My customer is still mulling over web downloads. I'm
pulling them into the 21st century and some execs are interested and some are
not.
From: "Nicolás Alvarez"
Sent: Wednesday, October 30, 2013 1:42 PM
To: "General discussion about t
Depending on what your custom environment is like as well... some gov shops
don't give out internet access... so downloading is not an option...
-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com]
Sent: October-30-13 2:38 PM
To: General discussion about the WiX to
Right. Any packages that are "beside" the bundle exe will be used
automatically and not be downloaded. It's good as allows me to use same bundle
as both a web installer and an offline installer just by including the packages
or not.
-Original Message-
From: Nicolás Alvarez [mailto:n
Understood. I spent several years of my life that I can't get back working in
a SCIF.
From: "Steven Ogilvie"
Sent: Wednesday, October 30, 2013 1:53 PM
To: "General discussion about the WiX toolset."
Subject: Re: [WiX-users] Burn Question
Depending
Hi, Can burn handle a mix of per-machine and per-user MSI packages? I thought
I read somewhere it can't but can't find it.
Wes
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: August-23-13 3:43 PM
To: General discussion for Windows Installer XML toolset.
Subje
That doesn't sound right. If a file can't be found, the BA is provided the
opportunity to provide the file via local file or URL. It is possible (haven't
looked in a while) that if a file is in a container the container must be
provided but that too can be provided by local file or URL.
-Or
Yes.
Note: the presence of a per-user package makes the bundle per-user.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Wednesday, October 30, 2013 12:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Burn bundle - mix of per
Thanks. That makes sense. I'm installing drivers so need to have both.
Can a per-user bundle upgrade or uninstall a per-machine bundle via
relatedbundle element's attribute Action set to Upgrade? I have a per-machine
bundle now. Thinking of switching my app to per-user.
-Original Mes
Installation of 1.1 will work with a minimum download of the 5 changed
packages if you create a web installer in burn including all 25 packages.
But what will happen with your installed version 1.0 in ARP? The entry will
stay there. If your 1.0 package gets uninstalled it does not care about the
de
This customer has a full install of 400MB (apx), doesn't deliver to nearly that
many customers and releases major releases once a quarter and updates every
2-3 weeks. Not all customers want the updates.
Personally I think they are on the fringe of a single MSI major upgrade being
OK but the c
I have a couple more queries regarding burn. Is there any way to password
protect the bundle? If so, what level of encryption is used?
Do download URL's support HTTPS? Is there any mechanism to support URL's
that require authentication? Is it possible to have the packages encypted
and dec
2013/10/30 Christopher Painter :
>
>
> And a rollback CA and a commit CA and. :)If that works for you,
> fine. I won't call it a 'bad thing'.We all have to do dirty things now
> and then, don't we? :)
>
> My personal favoring is setting the installdir to C:\Progra~1\ grin.
That's
Trust me, I know what I'm doing. :)
From: "Nicolás Alvarez"
Sent: Wednesday, October 30, 2013 5:42 PM
To: "General discussion about the WiX toolset."
Subject: Re: [WiX-users] Force replace files when applying patch
2013/10/30 Christopher Painter : > >
I believe I am getting an erroneous failure message when building a rather
large Wix project. The project contains a total of 27,654 files in it,
divided among 31 different cabs. However, after candle/light on the
project, I get a failure after about 6 minutes and no output files are
built. (No .c
Interesting, I'm sure I have the updates. I think I just installed Update
3 4-6 weeks ago. But I'll check my work machine in the morning.
On Wed, Oct 30, 2013 at 1:22 PM, wrote:
> See here:
>
> http://connect.microsoft.com/VisualStudio/feedback/details/731094/ghost-msbuild-exe-in-vs11-when-us
One of my sreens in ISWIX is the "Namespace" designer. It's a simple grid
with checkboxes that display extension prefixes and target namespaces. I
created this to make it easier to add references to things like the util
namespace without looking it up all the time.
All has been well and rece
1. Not today. Not sure what a BA could here on its own.
2. HTTPS is supported.
3. Authentication is supported.
4. No.
-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Wednesday, October 30, 2013 3:10 PM
To: General discussion for Windows Installer XML toolset.
That doesn't sound right. If Bundle v1.1 is an upgrade of Bundle v1.0 then v1.0
will be removed after v1.1 is installed. Reference counting should mean the 20
packages are not removed if Bundle v1.1 lists them (as I noted below).
-Original Message-
From: Markus Wehrle [mailto:mar...@laik
I honestly don't remember...
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Wednesday, October 30, 2013 12:22 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs
Thanks. That makes sense
Hi, folks.
Sorry to ask such naive (and honestly, non-WiX) questions, but...
when installing from an MSI, Windows Installer makes decisions on EXE files
based on the file version resource in the file, right?
I have a vendor releasing software to me where they've set the Product
version in their
Hi everyone,
I was wondering if I should open a ticket for this issue if noone has done that
so far...
Best regards,
Tobias
Von: Tobias Erichsen [i...@tobias-erichsen.de]
Gesendet: Montag, 14. Oktober 2013 17:11
Bis: General discussion for Windows Install
Second Burn window appears during Aladdin eToken driver installation
http://wixtoolset.org/issues/4140/
-Original Message-
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: Thursday, October 31, 2013 9:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
41 matches
Mail list logo
