Thanks for that, but it is only writing to file what ever is displayed in
the command window through other ICE(s) (ICE1 - 1CE100) performed by
darice.cub, but not those of my CA even through it can display in the
command window
Nag
_
From: Schrieken, Rene [mailto:rene.schrie...@logica
SourceDir property -
http://msdn.microsoft.com/en-us/library/aa371857(VS.85).aspx
It will be resolved to a root dir of the installation package (whatever it
might be - CD ROM or admin installation somewhere on the network share, etc.),
but be careful - you may get undesired prompts for source.
Close, but not quite as far as I can tell.
ExeCommand String This attribute specifies the command line parameters
to supply to an externally run executable. This attribute is typically
used with the BinaryKey attribute for a type 2 custom action, the
FileKey attribute for a type 18 custom action,
CA Type 34 - does it give me the D:\ drive (CD ROM Drive). If it does then half
problem is solved.
Yes, I wish bootstrapper - I do have it but got to remove it, well requirements
are that we need to install items on demand based on user selection.
Arun Perregattur
-Original Message-
So my code would be something like this
Does the Directory="SourceDir" exists?
Arun Perregattur
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Monday, December 28, 2009 5:49 PM
To: General discussion for Windows Installer XML toolset.
Subject
And, maybe I should point out that you might actually need two
CustomAction entries to run one program. Here's mine
The first one sets up the command line to use.
The second one is what actually gets run. Notice how ExeCommand points
back to the Property defined in the first one.
-Ori
You need CA Type 34
(http://blogs.technet.com/alexshev/archive/2008/02/21/from-msi-to-wix-part-5-custom-actions.aspx)
and use [SourceDir] (instead of [cdromdir]).
Still, bootstrapper is probably a better choice to install SQL prerequisite.
-Original Message-
From: Arun Perregatturv [ma
I do have a CustomAction that references the SourceDir for its data
files, but unlike yours the main executable that I run is on the Hard
Disk. Still, a working example might be of some use so I have pasted it
below.
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@n
Thanks, I will try that.
I was thinking of using a CustomAction to run the external program, which I
already do for creating a database from the installed folder, but all I wanted
is access CDROM drive (Source Drive) to execute a CustomAction. I thought that
can be done?
Arun Perregattur
-
Don't take what I said the wrong way. WiX is just an MSI authoring tool,
and as such has many of the same or comparable capabilities that
InstallShield does (I've used both and much prefer WiX). It's just that
launching one installer from within another is not something Microsoft
supports or allows
In InstallShield, its very simple I can literally launch any program using
LaunchAppAndWait(SOURCEFOLDER\SQLServer2008\setup.exe) but here I can't find
any tutorials or sample or even a code snippet to say you can do that.
Arun Perregattur
-Original Message-
From: Chad Petersen [mailto
You can't generally launch one install program from within another.
However, I am not familiar with the specifics of this scenario, so,
maybe?
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Monday, December 28, 2009 10:23 AM
To: General discussio
Anyone?
Arun Perregattur
From: Arun Perregatturv
Sent: Monday, December 28, 2009 10:15 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Install external program from CDROM drive
I searched all over the Wix but couldn't find anywhere how to install
application from cdrom d
IIRC, to build 64-bit you need the Windows SDK as well since it provides
some of the libs (I never understood why VS didn't ship them).
On Mon, Dec 28, 2009 at 1:53 AM, ricky sundrani wrote:
> Hi Rob,
> I tried to build the ext.build file using NANT 0.86 Beta, since i only
> require to rebuild Wi
Basically, yes.
On Mon, Dec 28, 2009 at 7:15 AM, Carter, Patrick wrote:
> Rob,
>
> Thanks for getting me started. I simply wanted to confirm some things now.
>
> When I use dark.exe - the output is three folders (binary, file and icon)
> and a .wxs file. The folders contain the files for the a
Yes, it is under development in WiX v3.5 (which means it may or may not work
very well right now... now is less working).
On Mon, Dec 28, 2009 at 7:31 AM, Jahanzeb Khan wrote:
> Bob or anyone,
> Would u know when this feature will be available? Is this currently present
> in 3.5 version?
>
> Tha
Bob or anyone,
Would u know when this feature will be available? Is this currently present in
3.5 version?
Thanks
Jk
- Original Message -
From: Bob Arnson
To: General discussion for Windows Installer XML toolset.
Sent: Wed Dec 23 00:01:04 2009
Subject: Re: [WiX-users] WiX, InstallShie
Rob,
Thanks for getting me started. I simply wanted to confirm some things now.
When I use dark.exe - the output is three folders (binary, file and icon) and a
.wxs file. The folders contain the files for the applications, etc... Is this
the expected and desired output?
To combine these, I
I searched all over the Wix but couldn't find anywhere how to install
application from cdrom drive.
I have wix install which should install SQL Server 2008 based on user
selection. Say, if user selects client install I don't have to install SQL
Server but if he selects Server install then I hav
Hi Rob,
I tried to build the ext.build file using NANT 0.86 Beta, since i only
require to rebuild WixUtilExtension.dll and WixUIExtension.dll. I am
currently using WIN2K3 and have VS2008 SP1 installed. But using Nant , i got
some errors. I modified nant.exe.config. But now the errors i see now are
On Mon, 28 Dec 2009 08:30:58 -
"Sean Farrow" wrote:
> Hi:
>
> Is it possible to build one msi package that runs natively on both
> 32and 64 bit setups using Wix? If yes how wouldthis be done? If no is
> it possible to set pre-processor defines with the votive ui for
> specific configuration
I don't think you can have one msi for both 32 and 64 bit machines. But you
can have a single .wxs file which produces two different .msi files
when compiled on different architectures. It does this by reading
environment variables or system variables.(PROCESSOR_ARCHITECTURE).
On Mon, Dec 28, 2009
Hi:
Is it possible to build one msi package that runs natively on both 32and 64
bit setups using Wix? If yes how wouldthis be done? If no is it possible to
set pre-processor defines with the votive ui for specific configurations?
Cheers
Sean.
23 matches
Mail list logo
