Are you building your bundle via the command line/msbuild, or are you using
Visual Studio? In your test bundle, are you force redirecting the build to
your wix build (instead of any installed version of WiX)?
Ex: In your MSI WixProj and your bundle WixProj.
<WixToolPath>Z:\$(VersionMajorMinor)\wix3\build\ship\x86\</WixToolPath>
<WixTargetsPath>$(WixToolPath)Wix.targets</WixTargetsPath>
<WixTasksPath>$(WixToolPath)wixtasks.dll</WixTasksPath>
<WixExtDir>$(WixToolPath)</WixExtDir>
In your MSI project, is the reference to the CA pointing to your build? (You
could also use Orca or similar to just manually replace the CA DLL in the MSI.)
Is a bundle required to reproduce the issue?
I always build via MSBuild, and I am able to generate a custom WixStdBA and
attach to it.
-----Original Message-----
From: Phill Hogland [mailto:[email protected]]
Sent: Wednesday, November 19, 2014 4:34 PM
To: [email protected]
Subject: [WiX-devs] [SPAM] Re: [SPAM] Re: [SPAM] Re: [SPAM] Debug delopment
story
I have continued to work on this issue every chance I get. I have tried many
approaches but have not found any way to attach a debugger that actually hits
my break point in RestartManager.cpp. (In this case I build a wix debug build,
and on same system I compile and run a simple msi with a WixstdBA bundle.
Whether I have 1) a message box in WixRegisterRestartResources (immediate CA),
or 2) a DebugBreak(), or 3) pepper the called functions in rmutil.cpp
RmuAddProcessesByName and RmuAddProcessById with
LogStringLine(REPORT_STANDARD,.....
In all of above cases, when I compile wix, then compile the test msi, the msi
runs, hits the 4592 problem and failed posting the following log messages, but
without hitting my breakpoint or additional log messages.
Action start 15:24:53: WixRegisterRestartResources.
MSI (s) (20!74) [15:24:53:839]: Note: 1: 2711 2:
WixRegisterRestartResources: Entering WixRegisterRestartResources in
C:\Windows\Installer\MSIA358.tmp, version 3.10.1115.0
WixRegisterRestartResources: Registering process name RmStreaming.exe with the
Restart Manager.
WixRegisterRestartResources: Error 0x80070005: Failed to register the process
name with the Restart Manager session.
CustomAction WixRegisterRestartResources returned actual error code 1603 (note
this may not be 100% accurate if translation happened inside sandbox) Action
ended 15:24:53: WixRegisterRestartResources. Return value 3.
Action ended 15:24:53: INSTALL. Return value 3.
The msi build log shows that candle and light are using paths to the
WixUtilExtension.dll in the debug build which I modified, but the project never
hits those changes.
Attempts to use MsiBreak result in attaching a debugger, and even though
symbols are loaded the breakpoints are never activated. It seems like this
should be a simple change to make as Rob suggested in the meeting, but if I
cannot figure out howto debug the code or use log messages, I do not have
confidence that I can make the change. I have previously step into my own
C++ CAs, but I am having difficulty understanding how to build the wix
source so that I can step through it.
Another side issue is that I can add the wixca and UtilExtension\wixext
projects to my solution and build them in the VS IDE, but I cannot add the
UtilExtension\wixlib to my Solution as VS says it has an invalid GUID format.
Also I extracted the code related to RmuAddProcessesByName into a console app
and stepped through that code (in the same scenario that causes a setup to
fail) without observing any problem. There are two instances to the tray app
running, one under a service account, and both pids are detected and returned
in the array, implying that the failure is downstream.
I don't want to fill the forum with noise but I thought I would provide some
update if anyone has any suggestions.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Debug-delopment-story-tp7597968p7598122.html
Sent from the wix-devs mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate!
Instantly Supercharge Your Business Reports and Dashboards with Interactivity,
Sharing, Native Excel Exports, App Integration & more Get technology previously
reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
