Maybe it would be better to implement a 'Import data' utility in the
application instead of a setup.
Dan
-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com]
Sent: Wednesday, October 19, 2011 3:38 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding
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
Detect the .EXE file exists using a FileSearch action and condition your CA
on the FileSearch action parent property see
(http://wix.sourceforge.net/manual-wix2/wix_xsd_filesearch.htm).
Dan
-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com]
Sent: Tuesday,
. JL
-Original Message-
From: Dan Vasilov [mailto:d...@rms.ro]
Sent: August-17-11 10:34 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Calling an url during install process
You can use a custom action for this. If you can implement a .NET
You can use a custom action for this. If you can implement a .NET
based CA your code can be very simple (use a WebClient instance to connect
to the URL). Make sure your CA displays a proper progress text, so while
your setup checks the URL the user knows the setup is not blocked.
In .NET you will use a BinaryReader or File.ReadAllBytes, if the
size of the file allows. Does this answer your question?
Dan
-Original Message-
From: Simon Chromow [mailto:simon.chro...@bewotec.de]
Sent: Friday, March 04, 2011 1:05 PM
To: wix-users@lists.sourceforge.net
6KB.
-Ursprüngliche Nachricht-
Von: Dan Vasilov [mailto:d...@rms.ro]
Gesendet: Freitag, 4. März 2011 13:29
An: 'General discussion for Windows Installer XML toolset.'
Betreff: Re: [WiX-users] How to read binary file content using c#custom
action???
In .NET you will use
an
easier time debugging hex machine code than the WiX/MSI process.
Message: 6
Date: Thu, 24 Feb 2011 11:05:01 +0200
From: Dan Vasilov d...@rms.ro
Subject: Re: [WiX-users] Error 1723
To: 'General discussion for Windows Installer XML toolset.'
wix-users@lists.sourceforge.net
Message-ID
It is very likely the .dll is not included in the MSI package at
build.
Another possibility is the .dll is missing some dependent .dll files.
-Original Message-
From: Colin LeMahieu [mailto:clemah...@gmail.com]
Sent: Wednesday, February 23, 2011 7:26 PM
To:
A custom action will do exactly what you need, but please be aware
your setup users will
shortly see a command window on the screen.
Are you configuring a WCF-based application? If so, you may want to
ask one of your .NET developers to implement a C#-based custom action to
You can implement the bootstrapper to launch the .msi package using
the command line
msiexec /I {package.msi} PROPERTY1=value1 PROPERTY2=value2.
However, if you do this, you have to manually manage all specific
scenarios (upgrade, uninstall, patch, etc).
A better solution
Set a property in the installer (for example, CA001STATUS) and then use the
property in the installer flow.
Return an error from the custom action only if the error should stop the
installation and you do not need to show the user a friendly error message.
Good luck.
Dan
-Original
The SourceDir is set by ResolveSource. The actions using this property
should be scheduled after this action (see
http://msdn.microsoft.com/en-us/library/aa371857(VS.85).aspx).
-Original Message-
From: daniel.knoep...@noser.com [mailto:daniel.knoep...@noser.com]
Sent: Wednesday, July
I would use a launcher .exe that can properly be launched from the setup.
Then this launcher would start your application.
Probably your executable has some particularity, the setups we've developed
with Wix properly launch the main executable.
Dan
Hello,
We need help with the following scenario: we use a BrowseDlg to allow the
user to select the installation path. On this dialog, if the following
sequence is executed, an invalid error message appears.
Sequence:
- Open the BrowseDlg
- Type the letter of a disk that
I've found out that this behavior is by design (see
http://msdn.microsoft.com/en-us/library/aa370749.aspx for information about
the PathEdit control).
The solution is to implement a custom Browse for Folder dialog.
-Original Message-
From: Dan Vasilov [mailto:d...@rms.ro]
Sent: Friday
I need to replace the FatalError dialog with a dialog of my own.
The setup is using a custom UI (see the source below).
However, if I simply remove the DialogRef Id=FatalError and insert the
customized dialog I get
ICE20: FatalError dialog/action not found in 'InstallUISequence' Sequence
You could use ProcessMonitor from
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx and
run the COM server registration process ( the command line is probably
{yourexename} /regserver ).
The ProcessMonitor will give you the registry keys accessed by the
process.
One option is to modify the Wix installer to deploy all .dll files in the
same directory as the application executable files.
I assume you mean .dll files (unmanaged) and not .NET assemblies.
This way you will never encounter integration issues again.
Dan
-Original Message-
From: Daniel
: Sunday, October 11, 2009 2:46 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action type 19 displays message over the
Welcome dialog
Dan Vasilov wrote:
DialogRef Id=PrepareDlg /
It's the PrepareDlg, which is shown modelessly during AppSearch
Thank you.
Dan
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, October 11, 2009 2:46 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action type 19 displays message over the
Welcome dialog
Dan Vasilov wrote
Hello,
We're trying to manage the database schema from an Wix-based installer.
There are many tables containing FILESTREAM columns. The database engine is
properly configured and the SQL script to create the table runs fine from
SQL Manager, however the installer reports an error:failed
Hello,
We have a Wix-based setup that must meet a set of pre-conditions. The
conditions are properly checked, however the error message is displayed over
the Welcome dialog. We've tried to edit the UISequence and show the
Welcome dialog only when the specified conditions are met, however the
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Dan Vasilov [mailto:d...@rms.ro]
Sent: Friday, October 09, 2009 11:04
To: wix-users@lists.sourceforge.net
Subject: [WiX
24 matches
Mail list logo
