Hi,
Any update regarding above issue?
Does anyone have experience such issue for log files?
Thanks and regards,
CD
--
View this message in context:
Hi,
One update to understand issue properly.
If we provide /log option during installation or un-installation,
log file with following name will be created.
log file name
log file name_incremental number_msi name (on 32 bit)
log file name_incremental number_msi name (on 64 bit)
example:
I am
In my stdba as shown above I have both 32 and 64 bit msi.
I am able to install and uninstall my product on both platforms.
Observation:
When I install product, on UI, there is processing: label.
Which shows the current processing module.
During installation, it shows name of 32 bit msi and
Hi,
Any updates regarding this issue?
with regards,
CD
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wixstdba-Not-invoking-right-msi-for-32-bit-platform-in-uninstallation-tp7598029p7598166.html
Sent from the wix-users mailing list archive at
Hi,
I created a bundle with a chained msi like below.
Chain
MsiPackage Id=msi2 SourceFile=chain_msi2.msi
DisplayInternalUI=yes EnableFeatureSelection=yes/
/Chain
first time installation i can select/deselect features in msi2.msi bcoz
DisplayInternalUI=yes . But
]
Sent: Friday, November 21, 2014 10:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WixStdBA Does not allow to modify the chained msi features
in maintenance mode
Hi,
I created a bundle with a chained msi like below.
Chain
MsiPackage Id=msi2 SourceFile
Thanks for the suggestion John.
I was really happy when i saw EnableFeatureSelection=yes option. I am not
able see its effect.
Now it seems to take bit tough turn for me. My Manager allotted me as a full
resource on this IS- WiX POC. ComPlus, windows services, MergeModules,
C#,CPP n vbs CAs,
Yeah Phill. I do agree for Johns suggestions. Thanks for the link too.
During fresh installation it is ok to select/deselect the
feature/subfeature through BA. VS2012 onwards the setup screen has
checkboxes for the featurs.
But i am really confused at,
1. How to restore the status of th
Hi,
I have created wixstdba for my installer.
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle Name=Bootstrapper2 Version=1.0.0.0 Manufacturer=Microsoft
Sorry that is typo.
I have applied the same condition as you mentioned in the reply.
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle Name=Bootstrapper2 Version=1.0.0.0 Manufacturer=Microsoft
I'm using the WixStdBA to conditionally install either a 32-bit or a 64-bit
MsiPackage.
When my 64-bit package is installed a 32-bit version of msiexec.exe is launched.
Is there way to force the 64-bit msiexec.exe to get launched?
My MSI has a custom action to check for a running process and
Hi
While reading source code for WiX Extended Bootstrapper Application, I'm
wondering if I want to replace this Theme manipulation (xml based) with
Win-Forms or MFC based UI, do I have to modify/rewrite all that or I can
simply use references of some library, just as in case of Managed
How can I hide the options ui during upgrade. Now the upgrade looks exactly
like a clean install.
I know you can use SuppressOptionsUI but that also hides the options on clean
install.
Hans
--
Accelerate Dev Cycles with
I'm using the wixstdba to create my bundle. When I run package_name.exe /?
I get an empty dialog box. How do I add help text?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wixstdba-help-dialog-tp7593720.html
Sent from the wix-users mailing
@lists.sourceforge.net
Subject: [WiX-users] wixstdba help dialog?
I'm using the wixstdba to create my bundle. When I run package_name.exe /?
I get an empty dialog box. How do I add help text?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wixstdba-help-dialog
@lists.sourceforge.net
Subject: [WiX-users] wixstdba help dialog?
I'm using the wixstdba to create my bundle. When I run package_name.exe /?
I get an empty dialog box. How do I add help text?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wixstdba-help-dialog
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()
.
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 realize
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
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 - LoadBootstrapperBA changes
: 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 works
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
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
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
to understand the program logic
in unfamiliar code.
Makes things really nice when the bug only surfaces in release builds smile/
From: n...@x2systems.com
To: wix-users@lists.sourceforge.net
Date: Fri, 16 Aug 2013 20:45:54 +
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 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 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:
As I step through the Wix 3.8.722 code I observe in:
src\ext\BalExtension\Wixstdba\WixStandardBootstrapperApplication.cpp
at line 916
LoadBootstrapperBAFunctions();
if (m_fPrereq)
{
hr = ParsePrerequisiteInformationFromXml(pixdManifest);
not using a managed
bootstrapper, you probably shouldn't be setting that variable (I didn't have
any problems with WixStdBA in 3.7 even with that set, though).
Sean
Date: Wed, 14 Aug 2013 10:21:29 -0700
From: phogl...@rimage.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WixStdBA
Using WixStdBA with WiX 3.6.
Is there a way allow custom command line parameters to set values of Variables
in the bundle?
Thanks,
Ian
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free
the command line parameter the default value that you set i.e.
Value=DEFAULTVALUE will be used :)
Steve
-Original Message-
From: Ian Williams [mailto:iawil...@microsoft.com]
Sent: August-07-13 7:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WixStdBA Command line
Can you share a chunk of the log file for that. I expect the issue is the
automatic retry code on errors is incorrectly catching this scenario.
On Mon, Dec 3, 2012 at 6:15 AM, Bruce Cran br...@cran.org.uk wrote:
Has anyone else found that the cancel button on the error retry dialog
in
On 04/12/2012 15:06, Rob Mensching wrote:
Can you share a chunk of the log file for that. I expect the issue is the
automatic retry code on errors is incorrectly catching this scenario.
[07E0:0640][2012-12-03T14:00:33]i301: Applying execute package:
package.msi, action: Install, path:
Has anyone else found that the cancel button on the error retry dialog
in WixStdBA doesn't work (in 3.7 RC)? I find clicking it displays the
same error with an OK button before just retrying anyway. The error when
this occurs is Could not access network location.
--
Bruce Cran
Should WixStdBA work on Server Core? It mostly seems to, but Options -
Browse isn't functional since Core doesn't have the common dialogs -
apparently it can be made to work by adding some flags
I never tried.
On Wed, Nov 21, 2012 at 8:16 AM, Bruce Cran br...@cran.org.uk wrote:
Should WixStdBA work on Server Core? It mostly seems to, but Options -
Browse isn't functional since Core doesn't have the common dialogs -
apparently it can be made to work by adding some flags
(
Thanks to Rob's input I have finally got same version upgrades working in my
version of WixStdba, for reference this is what I came up with:
BOOTSTRAPPER_RELATED_OPERATION m_Operation;
virtual STDMETHODIMP_(int) OnDetectRelatedBundle(
__in LPCWSTR wzBundleId,
__in LPCWSTR wzBundleTag,
Too bad I still can't figure out why my previous bundle won't complete the
uninstallation.
Thanks for the information I may just go with a native approach as well.
On Sep 22, 2012 11:06 AM, Neil Sleightholm n...@x2systems.com wrote:
Thanks to Rob's input I have finally got same version upgrades
On 10-Sep-12 22:14, Hoover, Jacob wrote:
When using Burn to deploy a rather large MSI (over 27k components), the
WixSTDBA doesn't provide granular enough feedback. I was pondering adding
ActionData messaging so the end user would be aware that the install hasn't
hung. Would this be a valid
When using Burn to deploy a rather large MSI (over 27k components), the
WixSTDBA doesn't provide granular enough feedback. I was pondering adding
ActionData messaging so the end user would be aware that the install hasn't
hung. Would this be a valid feature request with an associated patch? If
Hello,
I'm adapting wixstdba to use a standard Win32 wizard rather than themes to deal
with additional complex processing required during prerequisite checking,
requesting and encrypting credentials of databases and other external systems
and performing some post processing after the
On 05-Aug-12 03:54, Werner Strydom wrote:
The call to BalManifestLoad fails and the logs show Failed to load
bootstrapper application manifest..
It also includes an error code that would probably tell you why it failed.
--
sig://boB
http://joyofsetup.com/
Should WixStandardBootstrapperApplication.Foundation work?
I couldn't get this work, among the issues I had to specify LicenseUrl or
LicenseFile which shouldn't be required and even with these it still failed to
load the theme when I ran it.
Neil
Neil Sleightholm
X2 Systems Limited
On 13-Dec-11 19:17, Ian Williams wrote:
Is there any way I can keep the standard bootstrapper and get something like
selectable items?
No, WixStdBA doesn't support feature selection.
I've looked at http://wix.sourceforge.net/manual-wix3/wixstdba_intro.htm, but
the completely customizing
I'm trying to present the user with some options when installing my product at
the bundle level, so I can decide which MSIs I want to run. I'm using wix3.6
with WixStdba right now. Is there any way I can keep the standard bootstrapper
and get something like selectable items? Are there any
Is there a way to set the icon of the standard burn application form, maybe a
WixStdbaIconSourceFile variable?
Or can the form icon use the IconSourceFile icon?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdba-tp7055053p7055053.html
Sent
46 matches
Mail list logo
