Hi,
I have written a BA where the installing user answers/modifies default
configuration.
How can I pass the updated properties back to MSI?
E.g. The installing user changes the default InstallLocation, how can I
notify the MSI that it should use the InstallLocation from the BA?
Thanks,
dfox
--
As a part of installation process, I would like to let the user to pick
a license file,
and install (copy) it after the main installation is done.
I browse through the list of UI Controls that WiX provides, but I only
see the controls
that pick a directory. Do I have to write a custom component
Thanks James, good point.
The driver will be signed for production; it just isn't at the moment. I
shouldn't need the Legacy option.
I've been mulling over perUser vs. perMachine installs and my conclusion is
that there's no point in a per-user install because the user would need to be
an admin
Did you remember to set the Legacy attribute to "yes" on your Driver
element?
See http://wix.sourceforge.net/manual-wix3/difxapp_xsd_driver.htm for more
info. Specifically:
"Legacy YesNoTypeIf set to "yes", configures DIFxApp to install
unsigned driver packages and driver packages with m
Thanks guys for your tips.
I think I have made some progress here.
I thought I have previously told the whole story, but it doesn't seem that is
the case. I was trying to keep the story short.
My setup is like this, the dependent library is architecture specific, so I
have two helper projec
Are these two DLL's sensitive? Would you be willing/able to share them
with me to play with?
From: "Daniel Wenqing Cai"
Sent: Monday, January 16, 2012 11:45 AM
To: "chr...@iswix.com" , "General discussion for Windows
Installer XML toolset."
Subject
Rob,
In his post he mentions he's able to sucessfully deploy the two files
together to the GAC using GacUtil so I don't think there's any problems
with how the DLL's are currently built. I will admit I don't fully
understand this aspect of the GAC but I do that back around 2006 I did do
an
Companion file means something very specific in the Windows Installer. It
will not do what you want. The error you are seeing GAC'ing multiple files
is also standard Windows Installer behavior.
To do this, I think you'd need to find a way to correctly manifest the
related DLL so that it too can l
The previously mentioned error turns out to be the dreadful 1935 error. Any
tips that can help me move along will be much appreciated.
Thanks,
Daniel
From: Daniel Wenqing Cai
To: "chr...@iswix.com" ; General discussion for Windows
Installer XML toolset.
Se
In the "define pre-processor variables" area of the project properties (right
click the wixproj in solution explorer) you can set values for pre-processor
variables. These can be assigned the values of msbuild variables (preferably)
or hard coded paths.
-Original Message-
From: James Green
Since you are using a batch script, why not simply put your in a
separate file and then append the generated .wxs file to it to produce a final
.wxs file that is included in the installer. You can use the copy command to
append files by separating the source files with a '+' sign. For example:
Hey Dan,
Thanks for that, I just read the section on that just after posting to the
list. It works fine if I put it in the generated .wxs file but not if I put it
in the non-generated Product.wxs file so anytime someone reruns the batch file
this key bit of info will get obliterated ...
How c
Urgh! That sounds horrendous. That's a significant count of files!
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: 16 January 2012 16:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File
Hi James,
I have an idea ho
Hi James,
Preprocessor variables and WixVariable's are not the same thing. A preprocessor
variable is defined using . For example:
Preprocessor variables are handled much like the C preprocessor handles #define
macros.
Dan
-Original Message-
From: James Green [mailto:jgr...@mang
Hi James,
I have an idea how you were feeling about adding 2000+ files because I had a
similar situation with over 12000 files and more than 1000 folders. Glad to
hear you got it working! :-)
Dan
-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: January-16
Hey Again,
I'm not sure how to go about getting this working now, I've tried a few things
and I just get Undefined veriables erros:
I have in
Product.wxs
Then I have heat producing a fragment with -cg RInstall -var var.RFileSource
But the build fails saying that "Undefined preprocessor varia
Hi All!
I want to add path to my executable into %PATH%. But it must depend on how user
choose to install my msi: per-machine or per-user.
- I want to change system variable if it per-machine installation
- I want to change user variable if it per-user installation
I couldn't
Hey Dan,
Yeah, I've just gotten all this working, thanks. Just trying to get the file
source path all configured and working now ... installer joy! And indeed that
would be a drag!
james
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may
contain confide
Hi James,
I haven't used heat for quite a while, but I think you can use the -cg
option to get it to create a ComponentGroup containing all your components and
then include that component group in your Feature using a ComponentGroupRef.
Otherwise I think you have to use a ComponentRef to refer
Hi Dan,
Yeah, I'm just getting my batch command setup for this. It's building OK as a
fragment but I'm can't work out how to incorporate it into the features so that
it will actually execute during the install process.
James.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@q
Thanks & sorry.
I ALWAYS prefer a WiX solution :)
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2012 15:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File
Look at the Wix help regarding the "heat" to
Hi James,
You can use the "heat" harvesting tool that comes with WiX to generate an
initial WxS installer file for your 2000 files and 650+ directories and then
add that WxS file to your installer.
Dan
-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: Janu
Look at the Wix help regarding the "heat" tool. That will do the tedious
initial script generation for you. Then you can tweak it by hand to maintain
the diffs in future versions.
If you're not asking for a Wix-based solution then the Wix mailing list isn't
really the place to be asking. The cab f
I am building an installer with a device driver, to be installed with the WiX
difx extension. The driver is self-signed for testing purposes. I set my
element to
and everything seemed fine. However I reasoned that a device driver had better
be perMachine so I changed the InstallScope to per
Hi Peter,
Not sure I understand. I already have a "default" cab file for our application
declared like:
This currently contains all the application files for our file defined by hand
inside Component declarations within the script. The problem I'm trying to
solve is that I have another 'su
Add Compressed="yes" to the package element and EmbedCab="yes"
Cabinet="Product.cab" to the media element of your installer and it will
compress the files into a cabinet inside it.
-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:14
To: wix
Hi All,
I have a large set of files to distribute with our installer (1100 files) and I
was hoping to be able to do this with a zip file but that doesn't seem possible
(nor a good idea) so I was wondering if it was possible to use a cab file
instead?
I'm wondering if the Cab will also be able
Rob,
I have failed to get the to work. I think I need more time
to understand the tool's layers.
In the race for time I have done the following to at least get what is
needed to for the bootstrapper to work for now.
This way when the user canc
> From: b...@joyofsetup.com
> On 13-Jan-12 01:41, Peter Hull wrote:
> > Bob: would it be possible to have the burn engine signed (by Microsoft) in
> > the released WiX 3.6
> That would mean that the UAC prompt would show Microsoft as the owner of
> your bundle.
OK, I had thought the UAC prompt w
29 matches
Mail list logo
