You just add rows to a table that has BootstrapperApplicationData=yes.
The Binder will translate all those rows into
BootstrapperApplicationData.xml.
I feel like I missed some complexity in your situation.
On Thu, May 24, 2012 at 2:12 PM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
Has
On 24/05/2012 17:52, Wilson, Phil wrote:
Those top two are Visual C++ 2010 C runtime support Dlls, typically supplied
with this type of thing:
http://www.microsoft.com/en-us/download/details.aspx?id=
or with merge modules that came with Visual Studio 2010. You'll probably
need a
On 24/05/2012 16:49, Chris Robison wrote:
I've been trying to completely suppress any FilesInUse dialogs from
appearing, because I want to handle it. I've tried
setting MSIRESTARTMANAGERCONTROL=Disable, that seems to prevent restart
manager, which is good. I've also tried creating my own
Hi there,
I try to extract the self-register information for a COM file written
with VB6 a long time ago.
If I use regsvr32 to register the file manually on Win7 64-bit it works
fine. But when I try to extract the information using heat with the
following command line, just the file tag is
Is there any update?
On Sat, May 19, 2012 at 11:01 AM, Ravi Raj raviraj.callin...@gmail.comwrote:
Any suggestions???
On Tue, May 15, 2012 at 11:49 AM, Ravi Raj raviraj.callin...@gmail.comwrote:
I have done this thing:
Property Id=ENABLEVIRTUALIZATION Secure=yes /CustomAction
Hi,
Am tried to run the burn with classlibrary in bundle.wxs project, but am
unable to get the solution. I have followed the below sample.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-bootstrap-failing-to-load-td7547420.html
while running the application, the below log
Thank you, I appreciate all of your help
On Fri, May 25, 2012 at 3:24 AM, Rob Hamflett rob_hamfl...@sn.scee.netwrote:
On 24/05/2012 17:52, Wilson, Phil wrote:
Those top two are Visual C++ 2010 C runtime support Dlls, typically
supplied with this type of thing:
I want to customize my installer to have a disk cost dialog. I thought it
would be easy to check existing template. However, I really don't understand
how it works. In the WixUI_Advanced.wxs, it declares the dialog reference
like this:
DialogRef Id=DiskCostDlg /
But how does this dialog get
Hi Nick, Thanks again for your prompt response. I have pasted the dialog
portion of the modified VerifyReadyDlg below. For clarity, I made the
font-size larger where I added code. My Dialog is called the
DBCredentialsDlg. It should be spawned whenever the user clicks the
install,
Thanks Rob, it really was that easy.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, May 25, 2012 2:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom MBA, adding extra metadata to the
Bootstrapper
Is there a way to check for pre-existing products other than via
FindRelatedProducts? The problem I have is that regardless of the
operation (install/repair/remove) I need to discover if some of our
other products are installed, and FindRelatedProducts only runs on install.
Is there a way to
Notes I seen this
http://sourceforge.net/mailarchive/forum.php?thread_name=8701D1480741164DB71E42643C4A489F03380D86%40emeamail0305.global.sdl.corpforum_name=wix-users
Depending on whether you are using SQL Server 2008 or SQL Server 2008 R2.
The option /IAcceptSQLServerLicenseTerms is NOT a
Don't you have to specify what features to remove?
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx#Uninstall
Also to debug the Sql install check the logs that are created in the
installation dir (C:\Program Files (x86)\Microsoft SQL
Server\100\Setup Bootstrap\Log) they are very
Nope that wasn't it . Nothing in the SQL server logs.
Burn is checking if it is installed somehow and determining that it
isn't installed.
On Fri, May 25, 2012 at 11:16 AM, Richard Mayes caveman.d...@gmail.com wrote:
Don't you have to specify what features to remove?
Last year I wrote an installer to install a Windows service. Part of that
install includes a custom action which calls the executable which is
installed and passes in some command line parameters so that a
configuration file is updated.
However, the custom action started failing. I get the
So, assuming I put a cancel button onto my managed bootstrapper application
UI, can anyone say what's the best practice for carrying it out? Do I
somehow trigger a rolled back on the entire chain of packages? If so, what's
the method to call?
I've been looking through the WiX demo setup, but I'm
Did anyone resolve this issue? I am getting the same problem in Windows XP.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-detected-as-virus-RunOnce-registry-keys-tp7409683p7577248.html
Sent from the wix-users mailing list archive at
Heat does not extract for 64-bit dlls. We have had to write a script to
convert the 32 bit extraction into 64 bit.
From: Michael Scheepers mscheep...@tool-links.de
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
18 matches
Mail list logo