I need to get the version number for an msi from an exe file that isn't
deployed as item from the msi?Is there a way to get the file versione from a
file using his folder path?
in the same way I need to set the version of an exe setup package added in a
Burn setup to make it upgrading correctly.
Firewall Schema:
http://wixtoolset.org/documentation/manual/v3/xsd/firewall/
Util Schema: (User)
http://wixtoolset.org/documentation/manual/v3/xsd/util/user.html
I think what you're getting at is that you built a custom executable
that performs many of the tasks that the WiX extensions do rathe
It actually sounds like stuff that should be part the installation transaction
of a package so that it is properly rolledback/removed/etc.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Ori
Ok maybe I should phrase it in a more generic way. An exe that does more than
just enter info into a database. BTW, the "enter info into the db" part must
be done through the exe by using an exposed API installed as part of an earlier
MSI. This exe would do things like adjust firewall setting
Jacob beat me to the punch... That's what I get for being thorough lol.
Quoting "Hoover, Jacob" :
> Can you not do the same thing with a SqlScript element from the Sql
> Extension and eliminate the need for the Exe all together?
>
> -Original Message-
> From: robert_ort...@agilent.com [
Can you not do the same thing with a SqlScript element from the Sql Extension
and eliminate the need for the Exe all together?
-Original Message-
From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com]
Sent: Thursday, March 27, 2014 1:57 PM
To: wix-users@lists.sourceforge.net
Consider Using the SQL Extension documented here:
http://wixtoolset.org/documentation/manual/v3/xsd/sql/
This removes the need to run the Executable afterwords. Specifically, use the
SqlScript Element and Insert or Update your new data using T-SQL
Scripts. You can test them by running them is
Greetings,
I have an exe that needs to run at the end of installation. The exe itself is
just an app that runs and enters information into a databse which was installed
as a part of an earlier MSI in my bundle. This exe is NOT installed anywhere
on disk.
My question is, can I use the ExePack
...and repeating myself, if the concern is the error message in a previous post:
MSI (s) (88:78) [14:29:08:578]: Disallowing uninstallation of component:
{A5A114B9-ECE4-4EFE-8DE7-DA07E024554A} since another client exists
..then look up that id in the Component table of your MSI file and see
what
The general problem with shelling out to the command line type of
program/bat file is that you also shell out the error messages. If you
can write code to do it you can get a real error result. Otherwise
you're guessing like we are now. Assuming that the command is actually
correct and the files ar
I've tried to unsubscribe but it is not getting processed. Can someone help?
Thanks,
Jon
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.
Timiz,
You won't be able to place your exe within the install sequence of the MSI,
but rather you can run it after the MSI completes. Before going down the
chaining process, I would ask what configuration information it is that you
must do in an external application instead of with the already
Thanks Jacob,
Actually, my xx.msi package already have standard UIs.
But I still need to run one win form application(used for doing necessary
things) during the installation.
You can
So I considering to use bootstrapper to accomplish this task.
Unfortunately I only can chain the win form ap
13 matches
Mail list logo