pdb myself.
Neil
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 19 August 2013 14:38
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixStdBA - LoadBootstrapperBA changes m_fPrereq
Yes I had a similar problem setting a breakpoint, but I did not real
Yes I had a similar problem setting a breakpoint, but I did not realize it
was due to the pdb. When WinDbg launches the exe it breaks and gives me a
chance to set a breakpoint. I would not show the breakpoint that I tried to
set with F9 after placing the cursor at LoadBootstrapperBAFunctions() (
lease code I'll take a
look again. (You may want to raise a bug on the incorrect pdbs though.)
Neil
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 17 August 2013 18:48
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixStdBA - LoadBootstr
Or one could disable optimization in the Release build. We do this
frequently so that we can debug released code at a user's site using WinDbg
(with Release build dependencies). I am familiar with the effects of
optimization on debugging code. I also had my in-house WinDbg expert double
check my
ebugger to understand the program logic
in unfamiliar code.
Makes things really nice when the bug only surfaces in release builds
> From: n...@x2systems.com
> To: wix-users@lists.sourceforge.net
> Date: Fri, 16 Aug 2013 20:45:54 +0000
> Subject: Re: [WiX-users] WixStdBA - LoadBootstrapp
Just to clear, on XP I was using the debug build not the downloaded PDBs.
Neil
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 16 August 2013 19:17
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixStdBA - LoadBootstrapperBA changes m_fPrereq
Thanks for looking at this. I am still researching how to use git to get the
source code to make a debug build. I can also setup a XP test box next
week. I was working on localization issues using ProcessMon. I observed
some behavior where it would load my renamed logo.png file then it would
lo
Installer XML toolset.
Subject: Re: [WiX-users] WixStdBA - LoadBootstrapperBA changes m_fPrereq
I have taken a look at the code using WinDbg and see the same issue (using
Windows 7) but I think it is related to using WinDbg - If I do the thing on
Windows XP it works fine.
Has anyone else
: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 15 August 2013 16:06
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixStdBA - LoadBootstrapperBA changes m_fPrereq
Just to clarify, I'm not setting the m_fPrereq variable. I was just stepping
through the code to learn how it
A simple repo was create which has the same behavior. Bug 3357 was created.
I also had another thread at wixextba.codeplex.com which ended up discussing
this issue. I'm sorry for the double post and appreciate all comments.
--
View this message in context:
http://windows-installer-xml-wix-too
Just to clarify, I'm not setting the m_fPrereq variable. I was just stepping
through the code to learn how it works, and I can see that m_fPrereq is set
to zero in the constructor of the class, but under WinDbg I can see that it
unexpectedly changes in the call to LoadBootstrapperBAFunctions(); (a
Here's what I remember about 3.7, I haven't used 3.8. The m_fPrereq variable
is associated with a managed bootstrapper. m_fPrereq is essentially a boolean
specifying whether the magic Burn variable WixMbaPrereqPackageId is set (that
variable specifies the PackageId for .NET). Since you're not
12 matches
Mail list logo
