This mailing list has moved. Please sign up for the
wix-us...@lists.wixtoolset.org mailing list.
More information can be found here:
https://www.firegiant.com/blog/2015/7/21/new-wix-mailing-lists/
--
What does this part mean now the association between the application and its
model file is no longer established at installation?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original
I think this only happens if you indicate to delete registry tree. You can
definitely file the bug but this is probably one of those bugs where it won't
get fixed until someone actually needs the fix. So don't file the bug expecting
it to be fixed by itself. smile/
What does the bundle log file show?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: boroda [mailto:bo.ro...@mail.ru]
Sent: Thursday, July 16, 2015 7:25 AM
To:
Yes. There are very good reasons why Burn behaves the way it does today and
handling this case requires additional (non-trivial) code (not fixing existing
code).
___
FireGiant | Dedicated support for the WiX toolset |
The attached container is stripped (to save [often signification] disk space).
Look higher in the log to see what package is requesting to be cached during
uninstall. Probably an ExePackage.
___
FireGiant | Dedicated support for the
, Burn, and the ARP
Hi,
Added the issue ,
http://wixtoolset.org/issues/4822
We will try to contribute to the issue :-).
Thanks,
Sound
On Thu, Jul 9, 2015 at 10:02 AM, Rob Mensching r...@firegiant.com wrote:
Add feature to Burn
At least in WiX v3.10 (maybe v3.9) you can set the package cache location via
policy:
HKLM\SOFTWARE\Policies\WiX\Burn@PackageCache
That is a machine wide setting for users that need to move the package cache to
a different drive.
___
In this scenario, Bv1 needs to be repaired. Hard unsolved problem to do better
than that.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: speirscd
Ahh, the prereqba completed successfully. So the bundle was successfully
installed before being restarted to load the ManagedBA. That basically makes
sense.
___
FireGiant | Dedicated support for the WiX toolset |
Add feature to Burn.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: soundararajan dhakshinamoorthy [mailto:er.soundarara...@gmail.com]
Sent: Wednesday, July 8,
Playing with fire writing to the Windows Installer's private data but I don't
have other ideas if old chainer doesn't have a sharing mechanism.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
I was looking at HEAD. Bug fix in WiX v3.9 or v3.10?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: CastroAlicea, Edwin [mailto:edwin_castroali...@mcafee.com]
Lots of files in the folder?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: thomas.deboben@rohde-schwarz.com
[mailto:thomas.deboben@rohde-schwarz.com]
Sent:
Yeah, okay then. Resetting the ACLs on lots and lots of files can take lots and
lots of time.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From:
It appears the old MSI requires it's source (that's a big no-no on uninstall).
Can you successfully uninstall it directly (i.e. not via an upgrade)?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
Yes, MSIs declare the architecture they support. X86 MSIs can't write to x64
locations. MSIs that target Alpha (now long deprecated) can't install on x86 or
x64 or ia64 (also now deprecated?).
See the -arch cmd-line switch and Win64 attributes on various elements.
Burn handles minor upgrades.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Reuss, Matthias [mailto:matthias.mr.re...@sivantos.com]
Sent: Friday, June 26, 2015 6:20 AM
IIRC, there is a feature request open to do smarter binary diffing. If not,
seems like a reasonable feature request to open.
In either case, perhaps you would like to implement this feature? If not, you
will be waiting for someone else to do so.
I think this applies:
http://robmensching.com/blog/posts/2007/4/27/how-to-create-an-uninstall-shortcut-and-pass-all-the/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From:
Any BA can choose to allow same version upgrades. The wixstdba does not.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent:
Not today. Creating the same bundle with the same version just isn't something
wixstdba considers a real scenario today.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
Give it a Provides element from Dependency Extension to enable reference
tracking.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Edwin Castro
PS: WiX v3.10 is available now: http://wixtoolset.org/releases/
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent:
Yeah, nothing to be done but to be clear you might be unhappily surprised when
the original MSI is requested during an upgrade because Windows Installer can't
find the it in the cache.
Might want to stop deleting the cache. smile/
Nope. Easy enough for you to do it rather than force a feature on everyone that
doesn't need it.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Reuss, Matthias
If your app is system wide then you probably should set ALLUSERS=1.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Todd Hartman [mailto:t...@machmotion.com]
Sent:
See the ExePackage/@LogPathVariable attribute
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: Monday, June 15, 2015 9:09 AM
Component/@Guid must be globally stable (the global part of global unique
identifier should kinda' hint at that). Component/@Id must be stable for
patching/minor upgrades.
___
FireGiant | Dedicated support for the WiX toolset |
You should read:
http://robmensching.com/blog/posts/2003/10/18/component-rules-101/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: keith.doug...@statcan.gc.ca
No. ApplyComplete means the apply is complete. If you want something to
participate in the transaction put it in the Chain.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From:
Generally, roadmap stuff is discussed on wix-devs and the WiX Online Meetings
(since most of the drivers of the project show up there).
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original
It will probably work but you may hit issues building patches. Nothing
specific comes to mind. If you hit issue, you can upgrade using latest toolset
then start patching again.
Generally speaking, one should not change tooling when patching. That goes for
all tools, versions of Visual Studio,
Validating the provided .wixpdb actually goes with the .MSI seems like a good
idea.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Tunney, Stephen
The bundle can self-update itself.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Shal Philipp [mailto:luc2...@inbox.ru]
Sent: Wednesday, June 10, 2015 3:52 AM
To:
Note: patching can be very sensitive so we don't tend to make any guarantees
that changing toolset versions (even between minor versions) won't break
patching.
Major upgrades should always work (even between major versions).
_
Short
Try Packages/@InstallScope instead. It absorbs all those settings.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Carles Pina i Estany [mailto:car...@pina.cat]
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
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.
Run time, aka: install time, (#) vs. bind time (!) vs. preprocessor time ($).
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Ryan Waller [mailto:rwal...@microsoft.com]
No, definitely not. The security issues have been discussed here in the past.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Jiri Tomek [mailto:katu...@volny.cz]
Sent:
Why do you need a new UpgradeCode all the time?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Griesshammer, Christoph (GE Healthcare)
Yes, I read that. However, that doesn't say why you need a unique UpgradeCode
all the time.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Griesshammer, Christoph (GE
Yes, always update the Bundle. It vouches for the security of everything it
contains (hopefully, you sign your bundle).
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From:
Despite its name, UpgradeCode can serve other very useful purposes... like
detection.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: David Connet
This statement is not true:
Having the same UpgradeCode for 2 installers causes the installer to initiate
an upgrade instead of an additional installation.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
Yeah, ships passing in the night. smile/
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Griesshammer, Christoph (GE Healthcare)
File the bug. Burn (the engine) should never crash.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Uni Gauldoth [mailto:unigauld...@gmail.com]
Sent: Tuesday, May 26, 2015
Don't add a MajorUpgrade element.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Griesshammer, Christoph (GE Healthcare)
[mailto:christoph.griessham...@ge.com]
Sent:
See if BAfunctions in wixstdba can get you what you want. If not, would need to
create a new BA.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Tucaliuc Mihai .
IIRC, Burn should keep registration in ARP when the first non-permanent package
is installed (aka: there is something Burn would do). A RollbackBoundary after
the permanent packages *may* be necessary but my memory is fuzzy there.
_
Burn doesn't support MSIs that switch install scope today. You'll have to pick
one at build time.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Jeff Tyson
Sounds like a Windows Installer problem.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Miroslav Rodic [mailto:rod...@arco011.com]
Sent: Saturday, May 16, 2015 2:56 AM
Always possible. There's a probably a couple 100,000 lines of code in the WiX
toolset. Dropping .pdbs next to the tools and getting the resulting call stack
would narrow it down to which line of code is offending. Plus, knowing which
version of the WiX toolset would help too since the code
I guess Burn is resolving the variables in the InstallCommand multiple times.
Not sure there is a work around except to escape the values by hand. Probably a
reasonable thing to file a bug on but fixing it may be hard since it'd likely
be breaking behavior change.
I guess I'd expect if the util:CloseApplication is sending an
::MsiProcessMessage() that wixstdba would show it. Would need to look closely
at the code.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
Did you use MSIENFORCEUPGRADECOMPONENTRULES?
http://robmensching.com/blog/posts/2007/1/4/doing-a-small-update-or-minor-upgrade-in-msi-use/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original
Make a bundle:
http://robmensching.com/blog/posts/2012/6/25/b-is-for-bundle-and-thats-good-enough-for-me/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Gareth Price
wixstdba does not have support for that today.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Rajesh Nagpal (SQL) [mailto:rnag...@microsoft.com]
Sent: Tuesday, May 12,
In this case, a verbose log file would be more useful.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Scott Ferguson [mailto:scott.fergu...@a2ktechnologies.co.nz]
Sent:
Maybe it's the app compat filter driver redirecting you to ProgramData and
you're not actually in ProgramFilesFolder.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Scott
The Windows Installer does not and the .NET Framework does not. So nothing in
the WiX toolset does because it wouldn't work even if we did.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original
Custom BA could set the RequestState on the package correctly and avoid all the
issues you describe.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Patrice Bastien
Yeah, stop the madness. Admit a mistake was made and ship mandatory updates
to A, B and the already released C's via some other mechanism (Burn bundle?).
Then get on to a good path with the new C. Don't bring down your future by
trying to dig a deeper custom action hole.
Or run it from the per-machine Run key to be elevated.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Nir Bar [mailto:nir@panel-sw.com]
Sent: Thursday, May 7, 2015
You have to be elevated to install to ProgramFiles. Your per-user MSI never
should have been able to install to ProgramFiles unless you always launched it
from an elevated process.
_
Short replies here. Complete answers over there:
What did the log file say?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Cockerham, Gregory [mailto:gregory.cocker...@siemens.com]
Sent: Wednesday, May 6, 2015 8:29 AM
Why do you want to force a restart? Your application is safely gone. Those
files will be cleaned up whenever the users chooses to restart again.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
ERROR_ACCESS_DENIED. Permissions are such that not even the Windows Installer
can access the file. SYSTEM removed?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Mohamed
Hah, missed the network share thing. Doh! That's probably it. Machine will need
access.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Hoover, Jacob
Created and modified time stamp on non-versioned file different?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com]
Sent:
IIRC, there is a feature request open for that.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Tuesday, April 28, 2015 1:55
Windows Installer only ignores the 4th digit of the MSI version. It'll evaluate
all four places of a file version.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Lukas
No problem. This is what we do for our customers every day at FireGiant
(although FireGiant answers are far more detailed than the 1-2 sentences I have
time to write here).
_
Short replies here. Complete answers over there:
/
-Original Message-
From: Martin Cornelius [mailto:martin.cornel...@datron.de]
Sent: Wednesday, April 22, 2015 5:40 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Downgrading a Bundle ?
Rob Mensching-7 wrote
I would be surprised if wixstdba supported downgrades but Burn
Integrate what? It's an unimplemented feature request. There is nothing to
integrate until someone designs then implements the feature.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original
Nope. Hashing, yo!
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Tuesday, April 21, 2015 1:22 PM
To:
Sign the bundle?
http://wixtoolset.org/documentation/manual/v3/overview/insignia.html
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Mrugesh Patel
I would be surprised if wixstdba supported downgrades but Burn does. Did your
test below use wixstdba?
-Original Message-
From: Martin Cornelius [mailto:martin.cornel...@datron.de]
Sent: Monday, April 20, 2015 07:52
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
I think it's an open feature request not a bug.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: ssmsam [mailto:ssmcs...@gmail.com]
Sent: Friday, April 17, 2015 10:33 PM
To:
Why doesn't that work today?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Martin Cornelius [mailto:martin-cornel...@t-online.de]
Sent: Friday, April 17, 2015 12:54 PM
You should root cause why higher version Components exist on the machine since
you scheduled upgrade early.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Lukas Rieger
Hmm, now I'm confused. What is the issue now? You can certainly override the
default planning of packages in your chain via your BA. Not clear how that
solves the original issue.
_
Short replies here. Complete answers over there:
there: http://www.firegiant.com/
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Monday, April 13, 2015 8:59 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] How can I prevent Bundle from overriding MSI Upgrade
Code?
Not today:
http
Not today:
http://robmensching.com/blog/posts/2012/6/25/b-is-for-bundle-and-thats-good-enough-for-me/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: ben.lemond
Not clear to me how that would help.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Sent: Monday, April 13, 2015 8:29 AM
Possibly. Would need to understand the scenario well to make a recommendation.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: victorwhiskey
List all the files in the folder as Payload elements.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Roni Fuchs [mailto:ro...@microsoft.com]
Sent: Sunday, April 12, 2015
I expect A' is a major upgrade of A. There issue is that B knows nothing about
A' (and C) and C doesn't have enough information to install A when it
uninstalls A'.
In this scenario, a repair of B is necessary. Somewhere there was a feature for
C to automatically repair B (if there was some
We'll need Windows Installer team to change the way they implemented ICEs back
in 1998.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Anthony Foglia
I'd consider shipping the setup.exe (and any support files) in the bundle
without the archive wrapper.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: maverick02 maverick02
, and
installation?
Thanks.
- Original Message -
From: Rob Mensching r...@firegiant.com
To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net
Cc:
Sent: Thursday, April 2, 2015 12:51 PM
Subject: Re: [WiX-users] Using burn to download, unzip, install package
I'd consider
NETFX v4.5 is an in place upgrade of v4.0. If you have v4.5 you no longer have
v4.0 on your machine.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Lutteke, Robin
Often the Programs Features contains the name of the product which is
typically a trademark (or treated like a brand in any case) and thus not
localized.
It's possible to change the name but wixstdba doesn't really expose it easily.
,
Robin Lutteke
Software Engineer
Ringwade 1
3439 LM Nieuwegein
T +31(0)30 663 8000 (optie 1)
F +31 (0)30 663 8010
www.ordina.nl
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: maandag 30 maart 2015 18:17
To: General discussion about the WiX toolset.
Subject
so I don't make mistakes based on an incomplete comprehension - very wise.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Pat Blair [mailto:p...@daburu.net]
Sent:
Schedule your upgrade late and carefully adhere to the Component Rules.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Tobias Markmann [mailto:tmarkm...@googlemail.com]
RemoveFoldersEx?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Sarvagya Pant [mailto:sarvagya.p...@gmail.com]
Sent: Monday, March 23, 2015 9:05 AM
To: General discussion
1 - 100 of 5072 matches
Mail list logo
