If anyone else is interested I found and fixed the problem
In GamingExtension src\ext\GamingExtension\ca\gaming.cpp | SchedGameExplorer
// we need to know if the component's being installed, uninstalled,
or reinstalled
WCA_TODO todo = WcaGetComponentToDo(pwzComponentId);
This is
Digging deeper I also found this in the build logs
Unhandled Exception: System.AccessViolationException: Attempted to read or
write protected memory. This is often an indication that other memory is
corrupt.
at
Microsoft.Tools.WindowsInstallerXml.Msi.Interop.MsiInterop.MsiCloseHandle(UInt32
d
I have started getting this message periodically, and have not been able to
determine why.
I have verified that the user account as full rights to the temp directory (I
would expect nothing else); anyone have any ideas how to troubleshoot this?
The real problem is that it doesn't happen consi
I re-read some of the posts I found on Google, and in them they say to move the
custom action to "before CostFinalize" where I had before CostInitialize.
I made the change, and it worked. Not clear why it seemed to work partially
when done before CostInitialize, though.
Thanks
Mark
-Orig
Burn does provide a Variable (WixBundleLog) that points to the log location.
There is no "directory tag" so I'm not sure what you are referring to.
Ideally, I want a single location where logs are placed so that we can
easily ask people, "Please send us the logs from folder X" to start
debugging.
I'd like to be able to put this in the markup within the directory tag, and
then let WiX's magic decide how that is implemented; This way the log is
available and in a known location to the application for error reporting and
troubleshooting by anyone, and there's no risk of it getting deleted.
I am attempting to write new values to the Registry with a Wix
installer on a Windows 7 box. On the first installation the settings
are written properly, I then uninstall the application and find that
the Registry settings are still there (which is what I want).
When I try to install again, or use
That "Action: Null" is the root problem. The verbose log file should explain
why the Component is not being uninstalled.
On Thu, Sep 29, 2011 at 10:01 AM, M Angelo Duran wrote:
> I see removal of values from the key but no attempt to remove the key.
> (Note
> I used /l*vx unintall.log)
> The comp
Yeah, whatever you want to do.
On Thu, Sep 29, 2011 at 9:47 AM, Tom Quarendon
wrote:
> And so the point is that I then need to author my own dialog that gets
> displayed based on that property being set?
> Thanks.
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
The WiX.chm provides pretty good documentation about what the WiX provided
UIs provide. They don't support your scenario because no one needed it *and*
contributed it.
On Thu, Sep 29, 2011 at 1:20 PM, Tom Quarendon
wrote:
> I suppose I'm just slightly surprised I have to do this myself, that ther
I need your opinion.
Currently Burn logs to the %TEMP% folder by default (you can override it
with the -log/-l switch). This is great because most people expect this sort
of temporary data to live in the log file and Windows provides built in
mechanisms to clean out the %TEMP% folder should it get
I suppose I'm just slightly surprised I have to do this myself, that there
isn't some kind of user interface build in to do that notification. It's not a
problem, I was just trying to understand that I am indeed expected to do that
myself. It's often hard to tell with MSI/WiX what you're suppose
Hi
I'm trying to set up an install of multiple games from one package.
All games are optional installs.
When adding game explorer data using the gaming extension I get MSIHANDLE
leaks if some of the games (and therefore the gaming data) is not installed.
The leaks are during the WixSchedGameExplore
I can reference a component in two features if I want to make it install if
either one is selected. So that gives me an OR operation. What I want is to
install a component only if two features are selected, that is an AND. Any way
of doing this?
Thanks.
-
I see removal of values from the key but no attempt to remove the key. (Note
I used /l*vx unintall.log)
The component of the key reports this state in the log:
MSI (s) (7C:80) [11:02:22:515]: Component: MultiRegA; Installed: Local;
Request: Absent; Action: Null
Also UpdateEnvironmentStrings is
And so the point is that I then need to author my own dialog that gets
displayed based on that property being set?
Thanks.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 29 September 2011 15:59
To: General discussion for Windows Installer XML toolset.
Subjec
Dopes the verbose log file show why the key is being left behind. The remove
registry element should not be necessary.
On Thu, Sep 29, 2011 at 7:54 AM, M Angelo Duran wrote:
> *Background:*
> I have been tasked with creating a Windows Installer using WiX that can
> either install only a single ve
Hello,
An old version of our product's installation routine has created some
registry values that are interfering with the operation of our new
product version. These were created by a Custom Action running
regsvr32. The new installer of course uses output from Heat to
register the DLL in questi
If you use the MajorUpgrade element, it should set the WIX_UPGRADE_DETECTED
property. If you do your own major upgrade authoring, you can create a
property of your own choosing.
On Wed, Sep 28, 2011 at 1:58 PM, Tom Quarendon
wrote:
> I've been playing with understanding upgrading in MSI/WiX, but
*Background:*
I have been tasked with creating a Windows Installer using WiX that can
either install only a single version of the product or multiple copies of a
product. This is determined by a property that can be set either on the
command line or using a radio switch in the UI. This changes th
Thank you jhennessey for pointing out my original posting wasn't in the correct
sub forum and not on the mailing list. It was suggested I subscribe to the
mailing list and repost..so here we are.
I've got to the point in the help where it says "To be written".
After building, compiling
Hello,
We have to implement a setup that generates a large set of
.ini files. Is there a tool to automatically generate WIX fragments from an
.INI file?
Dan
---
I have successfully created a patch and msimsp detects the changed files.
However the only way I seem to be able to get the files to install is by
running the patch with REINSTALL=ALL which is not good because that seems to
force a reboot.
All the modified files are key files.
What do I need to d
23 matches
Mail list logo
