Hi there,
When I set the UAC to the default setting on Windows 7, I seem to get this
error when I try to run the uninstaller from Programs/Features
[0AFC:07A0][2011-12-14T15:53:26]: Plan complete, result: 0x0
[0AFC:07A0][2011-12-14T15:53:26]: Apply begin
[0AFC:0EB4][2011-12-14T15:53:26]: Error 0x
Is my understanding of the RegistryKey's action parameters incorrect?
Recently, we moved from having the keys with the Action parameter set to
'createAndRemoveOnUninstall', to 'create'. We were clobbering keys between
applications with this setting. When rereading the documentation, it is
unc
BUG# 3459433 created.
https://sourceforge.net/tracker/?func=detail&aid=3459433&group_id=105970&atid=642714
Jon W. McCain | Software Engineer - Install
phone & fax +1.317.715.8462 | jon.mcc...@inin.com
Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com
-Original Message--
Just to add my .02 cents
We do this by hand because of the inconsistencies with HEAT as you mentioned
due to missing dlls/dependencies. But the method we use is to install the
component, use InstallWatchPro to take a snapshot, run regsvr32, and then
analyze the machine. This provides the ne
Unless you really understand COM in depth, authoring all the COM elements
by hand will be a bear. I'd go with the Heat technique. Personally, I've
written a Winform application that monitors a folder and calls heat every
time a change in the directory occurs. The result is then thrown into a
As soon as my sourceforge account is verified, thought I already had one, I'll
enter a bug.
Jon W. McCain | Software Engineer - Install
phone & fax +1.317.715.8462 | jon.mcc...@inin.com
Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com
-Original Message-
From: McCain,
I just completed my test and verified in a basic install that just creates a
share using the util:FileSharePermission extension does indeed wipe out
existing permissions and resets with the combined permissions outlined in the
install. I say combined permissions as I added a new user to the comp
Thanks Peter. I am working on the suggestion of building a small install. But
I will try that as well.
Jon W. McCain | Software Engineer - Install
phone & fax +1.317.715.8462 | jon.mcc...@inin.com
Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com
-Original Message-
F
Hello, all!
Please briefly explain me (or give me a link to documentation) how to
register OLE server in WiX? I tried to find this information, but I could
not find anything.
Our developers provided me a .reg file with data required in registry on
target machine:
[HKEY_CLASSES_ROOT\CLSID\{000D0E0
You can view the result of a patched MSI in Orca by first opening the MSI
then using one of the menu items called "View Patch", if I remember rightly.
You could also extract the embedded transforms from the msp and look at those
but that's a little more work.
-Original Message-
From: McCai
Hi there,
I'm using Wix version 3.5.2519.0
When you create a diff patch of several previous releases, the delta can not
be specified in the pyro.
I'm using this cmd to create whole file patches successfully:
pyro.\v1.3.0\patch.wixmsp -out .\v1.3.0\Product.msp -t RTM
.\v1.3.0\Diff-v1.2.
11 matches
Mail list logo