What you have described is essentially what I am doing.
I have attempted the simple repro and of course, the simple repro does
not break. I made the repro attempt more and more complicated, but I
have not managed to break it yet.
The following is the single input file into a lib project. It has
I'm testing my installaition of device driver (with supporting other
components e.g. service and gui element). Currently doing test on WinXP
with installer on machine 3.01.4001.5512 .
I'm also using Wix 3.5.
Install portion works ok, everything looks like it's in right place.
On uninstall I get
We would like to be able to uninstall an older product, and install the new
version. I tried out the MajorUpgrade element, and it works well. The only
problem is that it seems to work silently .. apparently we need to be able to
prompt the user and ask them if it's OK to perform the upgrade.
You could use the Upgrade element rather than MajorUpgrade. That would give you
a Property you can use in a Condition to display a dialog asking the user if
they want to continue with the upgrade or exit the installation process.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141
Condition your dialog on WIX_UPGRADE_DETECTED.
However, is unattended upgrade or an install important? If it is, popping a
dialog during an upgrade scenario is going to force an attended install.
--
--
John Merryweather Cooper
Jack Henry Associates, Inc. (Premier Tech, Inc.)
Build Install
Has anyone got a set of blog posts that cover installing WCF
webservices using WiX? (Ideally for IIS 6, 7 7.5) I need to install
some https WCF webservices and after recently doing some manual
installs one area that I'm little concerned about is deciding which
certificate to use (and what the
Sending the error log without seeing the code that generated the error won't
get you any answers just more questions. Send along the code where you setup
the call to the CA and I'm sure we will find an answer.
-Michael
--
View this message in context:
I checked the InstallExecuteSequence table and located the
ScheduleStartRecorder action with this condition, which is correct:
VersionNT600 AND (NOT REMOVE~=ALL OR UPGRADINGPRODUCTCODE)
Here's the property:
Property(S): ScheduleStartRecorder = C:\WINDOWS\system32\SCHTASKS.EXE
/CREATE /F /TN start
I ran the ICE validation from ORCA, Examined the output to see if anything
related to the custom action and nothing did.
However - the bug is now gone.
As of two builds ago I am no longer seeing the installer in an
XP environment execute this CA - what changed. Pretty much nothing that
should
9 matches
Mail list logo
