Hi,
I'm calling a custom action on upgrade and delete of an application. The custom
action essentially deletes certain folders (not part of the installation
folder) using the command prompt.
When the msi is generated on windows 7/ windows 8, and then launched either on
windows 7/windows
Why reinvent the wheel?
http://wixtoolset.org/documentation/manual/v3/xsd/util/removefolderex.html
-Original Message-
From: sharada boda [mailto:sharada.b...@outlook.com]
Sent: Tuesday, September 09, 2014 6:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom action is
Ok, did some install testing of the upgrade from the earlier version to 1709
this morning.
Windows Server 2008 R2 No repro
Windows Server 2012 No repro
Windows 8 Reproduces
I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Enginee
Factor that may or may not mean anything:
Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop)
MajorUpgrade authoring is not being used (custom Upgrade Table entries)
Fa
By the way this also only seems to affect MinorUpgrade.
I tried out changing the product code to execute a MajorUpgrade, and indeed
the upgrade worked fine. So this further narrows it down and explains why
many others aren't seeing this, I guess MinorUpgrades aren't as common as I
thought?
// Sas
I figure it was a minor upgrade with the ProductCodes.
There was some expression of interest in a registry dump on my reproducing
machine for HKCR\Msi.Package. So, here it is:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:Sys
Just got this from Microsoft as a proposed fix:
http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 4
Microsoft forum, I should say.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: John Cooper
Sent: Tuesday,
Looking at the link, it would address the case where something was wrong with
HKCR/Msi or HKCR/Msi.Package, but the repro I had on Window 8 appears to have
the correct entries here.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
J
I noticed that your reproduction was only slightly similar to one of the ones
from earlier in the thread. The one earlier was an overlapped I/O, yours is a
hash being different.
Also, didn't some report problems with Windows 7, and your testing is on 8?
Keith Douglas
Statistics Canada | 170 T
That is true. Haven't gotten it to reproduce on any of our 7 Enterprise
machines. Did get the Windows 8 to reproduce. No luck on Server 2008 R2 or
Server 2012.
The Lyve installer was doing a minor upgrade with a non-standard REINSTALLMODE,
but that shouldn't have created the problem I repo'e
Okay I have another question about the masked edit field. If we have a PID
that contains only letters and numbers then is there a maskededit setting
that will ONLY allow this mix of characters or is this something that it can
not handle and therefore other actions would have to be used to validate
I am trying to write the detection logic for some VC redist packages (32
and 64 bit). The problem I am running into is being able to detect the
assemblies under windows\system32 on a 64 bit OS.
On a 64 bit OS, it appears that burn translates these as such:
[SystemFolder] => C:\Windows\system32\
[
The result returned by a rollback CA can be Success or Failure. But should
that response be ignored by the installer? If I check it, and it is a
Failure, will that prevent the installer from rolling back?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble
In a deferred custom action, I am changing some text in a file. I want to be
able to undo those changes in a rollback custom action. So, I'm attempting
to store the original contents of the file and then set the file back to
that data in the rollback CA.
The place where I've tried to store the ori
Hi,
Do you mind posting the fix in the xml file?
I have a problem doing a burn upgrade.
Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installer-upgrade-does-not-work-tp7589150p7596741.html
Sent from the wix-users mailing list arc
2014-09-08 16:44 GMT-03:00 Hoover, Jacob :
> As for the borked bundle, I'm not certain if you can easily assign the bundle
> Id, but that’s what I would try doing
> (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UpgradeCode-td7578845.html).
> I'm guessing you'd have
If you select to ignore by return=ignore but if you have return=check and your
CA fails, the installation rolls back.
The rollback though might not rollback your custom action's that have occurred
before the CA that failed.
--Pavan
-Original Message-
From: Nick Ramirez [mailto:nickra...
I wasn't able to find a way to pass data from a deferred CA to a rollback CA.
Nor could I access the session's database, which prevented me from storing
the data in a custom table.
The only way I found that worked was to store the original file in the TEMP
directory and, in the rollback, restore t
The "correct" way is to read the file from the immediate custom action and
schedule the rollback and deferred actions with the appropriate data. The WiX
custom actions do this all the time.
_
Short replies here. Complete answers over t
Hi Hoover,
The reason why I’m using custom action and calling command prompt and not
RemoveFolderEx is because I need to:
Always delete the folder on uninstall (which will work with removeFolderEx)
Delete conditionally on upgrade (i.e. I have modified the UI and provided a
checkbox in Install
Hi Dave,
I have done this with a different Approach.
I have used an Msi Product Check to Check for existing redist Packages.
To make sure the 64Bit Versions are not installed set the 64Bit flag within
burn.
I search for product ids with Microsofts Old Manifest bootstrap Editor. Don't
know if th
22 matches
Mail list logo
