I don't know what in Burn would lock existing files. Burn is very
self-contained and only uses files it carries with it, although a custom BA
can do anything. If you haven't already, I'd recommend using Process
Monitor to see if what locks your files when they are trying to be removed.
I'd be very
I sent email end of last week noting big infrastructure changes to website.
We're still working through those changes. It should be all good again
by end of day Monday.
On Sun, Jun 30, 2013 at 6:11 PM, Phill Hogland wrote:
> FYI - Tonight when I click on the button "Wix v3.7 released! Download>
After posting the above question, I thought maybe I should post the 'answers'
that I have been contemplating based on the research I have done.
Assume will always do Major Upgrade
1) in Release 1.0 create a component for dll_ver1.dll.
2) In Release 1.1
a) delete the component for dll_ver1.dll fro
I realize that this question is probably more a MSI question rather than WiX.
I have searched but did not find discussions of this specific issue that I
am sure is a common issue. Say I do a release of a product that has a
number of dependencies, some of which have a version number in the name of
I know about those, but how do I use them to prevent Burn from locking the
existing files before it runs the installer package to MajorUpgrade?
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: June 30, 2013 20:54
To: wix-users@lists.sourceforge.net
Subject: Re: [
FYI - Tonight when I click on the button "Wix v3.7 released! Download>>" at
wixtoolset.org I get Error 404m file not found. I tried several times
tonight. However under the release announcement post lower on that same
page is a link to the Wix 3.7 which works. Maybe there are some changes
being
Maybe this blog would be helpful:
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrade-uninstall-restart-issue-tp7586315p7587020.html
Sent from the wix-users ma
I am have a strange problem with feature selection and a push button
In general, if you keep the Package@InstallerVersion="301" ( Windows
Installer 4.x+ isn't available on Windows 2000 ) and avoid or carefully
test the use of extensions ( typically inject C++ custom actions ) you
should be fine.
>From a business perspective, I'm not even being asked to support S
9 matches
Mail list logo