That's much better, but I still needed the code that reads the InstallLocation
into my property.
Thanks!
> -Original Message-
> From: jhennessey [mailto:jack.hennes...@hyland.com]
> Sent: Wednesday, September 29, 2010 10:10 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-us
that reads that registry key into INSTALLLOCATION,
like so:
INSTALLLOCATION gets set to the default value if the registry value doesn't
exist, and gets set to the right value if it does.
Thanks for your help!
> -Original Message-----
> From: Younie, Bradford
> Sent:
tegrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Younie, Bradford [mailto:bradford.you...@chasepayment
I'm using the WIXUI_INSTALLDIR functionality in my installer. When I install,
it lets me change the install directory from the default path that I set to
INSTALLLOCATION and it installs to that new directory perfectly fine. However,
when I enter maintenance mode (by hitting Change in Add/Remove
This is with WiX 3.0.
I have an installer that has a COM component. I'm using heat to harvest the COM
configuration from both the DLL and TLB files into a fragment that I then
include in my wix build. This works great.
Now, I need to produce a 64-bit version of the same product, but I build it
I have two flavors of the SDK product that my company produces. I offer
a merge module for each flavor to our VARs so that they can work the one
they want easily into their installers. So far so good.
I also provide a single installer for our normal customers that lets the
user select which flavo
> I've copied the WelcomeDlg.wxs file to my area, renamed it,
> modified it to replace the bitmap, and updated its
> InstallUISequence so that it appears as it should.
>
> The only problem I have is that the original WelcomeDlg
> that's in the WixUIExtension.dll displays for second or two
> b
I've copied the WelcomeDlg.wxs file to my area, renamed it, modified it
to replace the bitmap, and updated its InstallUISequence so that it
appears as it should.
The only problem I have is that the original WelcomeDlg that's in the
WixUIExtension.dll displays for second or two before being replac
I have my own custom dialog sequence and I need to insert an
InstallDirDlg into it. WixUIExtension.dll has one, but every attempt I
make to fit it into my existing custom dialog sequence fails. It seems
to want to force me into using their canned sequence rather than my own.
Is there a series of
> Why are you trying to re-write this when it already exists in
> WiXUIExtension?
First, I have to say that I'm fairly new to wix. That being said, here's
my situation:
I have my own custom dialog sequence. I have my own WelcomeDlg, which
has its own banner bitmap. It currently goes to a custom
I'm trying to create a dialog that only asks for the destination
directory. I have it display the contents of INSTALLDIR, and the Browse
button works fine. The only problem is that when you OK the Browse
dialog and get back to the Destination Folder dialog, the label that
displays the selected path
> The IDs of components have a scope of the containing package.
> The Guids of components have a system-wide scope. As a
> result, you do need to fix this as soon as you safely can.
Thanks! That makes things a whole lot clearer. I wanted to understand
how it works so that I knew what my options
This is kind of a high-level question about components that I need to
understand:
What would happen in this scenario:
I have two installers that install the same file to their own directory
tree. When I defined each installer source, I did a copy/paste of the
component for that file from one so
> My guess is you need a
> somewhere in your mymodule.wxs file to pull in the fragment
> in your Templates.wxs file.
That did the trick! I created a ComponentGroup in the Fragment, and then
added a ComponentGroupRef in the Module.
Thanks for all your help!
Brad
--
Learn more about Ch
> My guess is you need a
> somewhere in your mymodule.wxs file to pull in the fragment
> in your Templates.wxs file.
Okay. I'll try that.
> What do you mean by " If I do the same thing to include them
> in my main installer, it works fine."? You change
> for and it works? Or what specifica
I'm developing multiple merge modules that share some data files in
common. I want to have the data files defined in a Fragment that each
merge module uses. For some reason, the files in my fragment doesn't
install, even though it builds with no error. If I add the fragment to
the main installer, i
> > Have you tried using INSTALLDIR instead of TARGETDIR?
> >
> > It should match the configurable directory of your application:
> > > Display='expand' Level='1' ConfigurableDirectory='INSTALLDIR'>
> >
> > Because that is the property that gets sets when the user chooses a
> > folder to ins
> Hi,
> > In a merge module, I'm trying to create an environment
> variable that
> > contains the path to where the product is being installed
> to. My merge
> > module uses the code below to do it, but it's not working
> quite right.
> > When the product gets installed to "c:\program
> files
In a merge module, I'm trying to create an environment variable that
contains the path to where the product is being installed to. My merge
module uses the code below to do it, but it's not working quite right.
When the product gets installed to "c:\program files\mycompany\myapp",
[TARGETDIR] in th
I'm fairly new to WiX and am trying to do use merge modules for the
first time (I'm fluent in InstallShield, but want to move away from it).
Anyway, I'm trying to have my merge module create a couple of
environment variables at install time, both of which will have
[INSTALLDIR] as part of its va
20 matches
Mail list logo
