Thom, where is the InstallUISequence in you example?
Here is my current code. This is the only UI element in my main product wxs:
This is the entire body of the SkyUI_Minimal.wxs file that is included in my
project (unchanged from WixUI_Minimal except the name):
http://schemas.microso
Notice that Rob said "schedule custom action". You need a custom action that
runs immediate whose whole responsibility is to schedule your rollback and
install custom action.
Likewise, you'd need the same trio of custom actions for uninstall.
ScheduleUninstallCA (immediate)
UninstallRollbac
I don't understand the "upgrade from the same version to the same version"
comment. That isn't an upgrade, the versions are the same. If the
ProductCode is the same, the Windows Installer should have automatically
gone into maintenance mode where the Installed property is true. I think
that can get
Delta patching has all sorts of issues. I honestly don't know the state of
delta patching in WiX v3.0 but my memory suggests that there were changes in
WiX v3.5 for delta patching. I'll have to ask Peter Marcu since he built
most of that system and doesn't hang out here.
On Wed, Jan 5, 2011 at 2:4
The schedule custom action should look at the Component states and write the
appropriate rollback data (rollback data first) and execute data (this
second). That way, the rollback stuff is in the installation script before
the execute stuff and when an error/cancel occurs during/after the execute
s
Unfortunately, no.
That build was a (now very old) intermediate release. We don't save
intermediate releases for very long. We don't have the resources to support
drops at all points in time of the development cycle. If you're using the
the "development branch" of the WiX toolset (which both WiX v
Take a verbose log and see what it says around any FindRelatedProducts actions.
I think you'll find that some CRT MSMS explicitly specify an ALLUSERS=1 value
to force per-system installs, and you may have been all per-user previously.
The cross-context upgrade per-user to per-system won't work.
Hi all,
I have the requirement to change the installer to do the following:
- on first install to give the user the chance to choose the
installation directory
- on updates _not_ to give the user the option to chose the installation
directory (the directory used for the previous installation wil
Hi:
Ok, given this limitation of deferred execution custom actions, how in mu
custom action definition in wix source can I only schedule the custom action to
execute if a component is being acted upon.
Essentially, what value does the component state equal when a rollback is
occurring?
Any help
Well, WiX is used to build MSIs (and MSMs etc). It can certainly build
MSIs that uninstall old version/upgrade to new version including
services and adding new files. But you'd have to do the rest yourself
(AFAIK?)
Have you not looked at ClickOnce?
http://msdn.microsoft.com/en-us/library/s22azw1e
This is how I do it in my (working) customized minimal UI, using WiX
3.5...
In the main Product wxs:
My customized UI wxs (which, coincidentally, simply removes the Welcome
dialog from the standard minimal UI. So I'm not trying to do exactly the
same thing as you...):
I think this is what you're after.
To reinstall even if the same version is already installed, I use this in my
Upgrade node:
The important part being IncludeMinimum="no" when looking for "newer" versions,
and IncludeMaximum="yes" when looking for versions that can be upgraded.
It generates
12 matches
Mail list logo
