My solution to this problem was to write a helper executable that launched
whatever command it was given as an argument within the folder in which it
was placed.
ExePackage
SourceFile = $(var.Launcher.TargetPath)
InstallCommand = 'arh.exe -installAppSilent MyApp.air'
I bundle an Adobe AIR app in my installer. Adobe provides this arh.exe tool
that can install, uninstall, and detect applications; I call it on
InstallCommand and UninstallCommand. However, I am at a loss as to how I can
call it to provide DetectCondition.
ExePackage
SourceFile =
Hi,
I am just porting one of our setup projects from Visual Studio Setup
Deployment to WiX. So far everything looks good, but I have one major problem.
There is an example subdirectory in the installation directory. I have to
install a shortcut to this directory in the start menu of Windows.
This is how I do it:
!--Setting up the shortcuts for the product--
Directory Id=ProgramMenuFolder Name=Programs
Directory Id=ProgramMenuDir Name=$(var.ShortcutName)
Directory Id=ProgramMenuSubFolder Name=LOGGERS
/Directory
/Directory
Try adding CreateFolder to the shortcut component, or put CreateFolder in
its own component and put it under the API_DirExample directory.
-Original Message-
From: Budde, Marco [mailto:bu...@telos.de]
Sent: 05 December 2012 10:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Add this to ensure that the custom action data is hidden as well:
Property Id=ExecXmlFile Hidden=yes/
Thanks for your help, but it helps to hide only one place with passwords in log.
But I still have some places with passwords:
. . .
MSI (s) (0C:80) [15:27:09:048]: Executing op:
That sort of configuration is best moved out into the application or a
configuration utility so that you don’t have to reinstall should it ever need
to change. It would solve your problem.
-Original Message-
From: Grigory Konovalov [mailto:grigory.konova...@confirmit.com]
Sent: 05
I am exploring moving a moderate size installer to WiX and I am stumbling
through with some good successes thanks to the active support community out
there. My application has a large amount (~1gb) of reference data that does
not change much from version to version. This data is not required
Hi,
I want to run Sql commands through Wix,like insert,update,create.
How to run sql commands through Wix.
Suggest me
Thanks,
Chaitanya.
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely
Hi,
It's really up to you, but there's a couple of things to consider:
* Would the reference data ever be installed without the main application?
* How do customers get hold of your application and the reference
data, and relevant updates?
* Have you looked at patching?
Normally, in your
See the Sql elements in the wix.chm.
On Wed, Dec 5, 2012 at 5:10 AM, Chaitanya chaita...@pointcross.com wrote:
Hi,
I want to run Sql commands through Wix,like insert,update,create.
How to run sql commands through Wix.
Suggest me
Thanks,
Chaitanya.
The CustomAction element needs a HideTarget as well. That'd be a bug in the
WiX toolset.
On Wed, Dec 5, 2012 at 4:21 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
That sort of configuration is best moved out into the application or a
configuration utility so that you don’t have to
I would definitely consider using a Bundle for your scenario. I believe the
world is moving (has moved?) to a place where .msi files are building
blocks stacked together and wrapped with a bootstrapper (Burn Bundles in
WiX toolset). You do need to think about the problem a little differently
when
Running an executable to do detection isn't supported today. Detection is
designed to happen based of static data on the machine.
On Wed, Dec 5, 2012 at 12:31 AM, Don Reba don_r...@inbox.ru wrote:
I bundle an Adobe AIR app in my installer. Adobe provides this arh.exe tool
that can install,
On 05/12/2012 15:15, Rob Mensching wrote:
I would definitely consider using a Bundle for your scenario. I believe the
world is moving (has moved?) to a place where .msi files are building
blocks stacked together and wrapped with a bootstrapper (Burn Bundles in
WiX toolset). You do need to
GPO is a usually casualty when using Bundles. Automated deployments with
Bundles need to use something more powerful like System Center. I worried
about this much more before both Microsoft Office and Visual Studio moved
to a bootstrapper/bundle-like system.
On Wed, Dec 5, 2012 at 7:45 AM, Bruce
Hi
I'd like to move a setup (that has only one pre-req) from MSI UI to
bootstrapper UI.
To achieve it, should I have to create my own wixstdba? I ask this
because I need a UI with many pages, each one customized, so I cannot
re-use the standard one.
Does it make sense to do all the UI in the
Yes, create the UI in a custom bootstrapper. The separation is: data
collection goes in the bootstrapper; modifying system state goes in the MSIs.
-Original Message-
From: up2date.cyb...@gmail.com [mailto:up2date.cyb...@gmail.com]
Sent: 05 December 2012 16:48
To:
So conditions like install on at least WinXP SP3 should be done in the
bootstrapper and removed from my MSI, right?
Should I move actions like closing running application from the MSI to
the bootstrapper too, and all things that could display any dialog/msgbox?
thanks for the answer
On
You do want conditions like that in the bootstrapper because the user doesn't
want to enter pages of information before being told, you can't.
However, if there's any chance the MSI will be used outside the bootstrapper,
keep them in that too.
Actions that require user interaction either will go
Doesn't bootstrapping cause problems for admins who are trying to deploy
software via GPOs?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, December 05, 2012 10:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
I have an application (.exe) that has a built-in automation interface.
I tried using heat to generate wxs code for the application, expecting
it to generate code to register the automation interface.
Unfortunately, it only generated code for the .exe file itself.
Is there a way to make heat
Thanks for the replies it will help me.
I also guess that launching app exe once install is successful should be
part of the bootstrapper.
On 05/12/2012 18:40, Peter Shirtcliffe wrote:
You do want conditions like that in the bootstrapper because the user doesn't
want to enter pages of
Yes, see my previous comment. smile/
On Wed, Dec 5, 2012 at 9:41 AM, Katherine Moss katherine.m...@gordon.eduwrote:
Doesn't bootstrapping cause problems for admins who are trying to deploy
software via GPOs?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Not today. Heat can't harvest selfregistration code out of executables.
Some people posted using a series of tools to do this sort of thing in the
archive. Or, you can just enter the Class, AppId, etc elements yourself. I
do the latter usually.
On Wed, Dec 5, 2012 at 10:48 AM, Dave Gilmour (FET)
I am unsuccessfully trying to get my installer to configure the recovery
options for my Windows service. I am using the WIX ServiceConfigFailureActions
element and the Failure element(s). The only Failure action that works for
myself is runCommand. If I use restartService or restartComputer;
ths link might be correct in 3.7 but there seems to be a problem with the
certificates there
here's a install log with the relevant info ( any idea what the correct
info needs to be? )
[0EC0:20D8][2012-12-05T14:22:34]i320: Registering bundle dependency
provider:
The CustomAction element needs a HideTarget as well. That'd be a bug in the
WiX toolset.
I tried to solve a problem with ExecXmlFile by this way.
I have just changed a type of ExecXmlFile custom action in the result msi file
from 3073 to 11265 (open it by Orca and add 0x2000 to the default
Hi,
Iam assigning permissions to Registry.(Admin-Fullcontrol,User-Read)
permissions.
Iam using code like.
util:PermissionEx User=Orchestra_User_Access Read=yes
ReadPermission=yes GenericRead=yes GenericExecute=yes
ChangePermission=yes /
util:PermissionEx User=Orchestra_Admin_Access
29 matches
Mail list logo
