Latest build of Votive is 3.0.5106.0. Try updating it & see if it fixes your
issue -> http://wix.sourceforge.net/releases/wix3.feed
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate wit
http://wix.sourceforge.net/releases/wix3.feed
To me it's missing the change lists for 06 April 2009 & 07 April 2009
builds. I'm viewing it using IE7's built-in RSS feed viewer on XP64SP2
(both fully up to date with MS Updates). No bells or whistles added.
Anyone else see the same or different?
Ch
WriteRegistryValues isn't a Custom Action
http://msdn.microsoft.com/en-us/library/aa372891(VS.85).aspx
The answer in that case would be no, if indeed WriteRegistryValues does
open command prompts (which I'd be very surprised if it does).
Palbinder Sandher
Software Deployment & IT Administrator
Try using a public property for the Edit control ->
http://msdn.microsoft.com/en-us/library/aa370912(VS.85).aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated
Looking at the InstallDirDlg.wxs available in the WiX 3.0 sources
(http://sourceforge.net/project/showfiles.php?group_id=105970&package_id
=16) you may want to set Indirect="yes" on your Edit Control and
change it from an Edit to a PathEdit.
Palbinder Sandher
Software Deployment & IT Admini
The WiX.chm file has a section in the How To Guides on Shortcuts. It
explains all this in detail.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental
You may want to actually change the version number too. I suspect this
is where most of your issues are coming from.
*New Version (1.0.1.1) source snippet:*
And you don't need to use CustomActions to prevent downgrading. That's
what the tag is for.
Palbinder Sandher
Software Deployment & IT
Author an ExitDialog?
http://msdn.microsoft.com/en-us/library/aa368569(VS.85).aspx
Or use one of the standard WixUI libraries to do it for you?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + In
On the issue with the files not being removed, I would check a verbose
log file & see what the problem is. Install your product using "msiexec
/i /l*vx " & install it to somewhere like
C:\TestMyApp or something (you could use "msiexec /i /l*vx
/qb MYAPPFOLDER=C:\TestMyApp" to skip the UI). The
Resending your question 3 times in a 7 hour period isn't going to get it
answered any quicker even if you do use different subjects on each post.
Especially when the day you're posting on is a holiday in most of the
world.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 94
UpgradeCode ->
http://msdn.microsoft.com/en-us/library/aa372379(VS.85).aspx &
http://msdn.microsoft.com/en-us/library/aa372375(VS.85).aspx
LaunchCondition ->
http://msdn.microsoft.com/en-us/library/aa369752(VS.85).aspx &
http://msdn.microsoft.com/en-us/library/aa369752(VS.85).aspx
Works for us. No
As Simon Dahlbacka said, no.
An MSI has to target a specific platform which has to be either "Intel"
(aka Win32 or x86), "Intel64" (aka ia-64) or x64 (can also be AMD64 but
this is deprecated to x64).
An x86 MSI can't target x64 specific directories. Try it & if you look
at the logs you'll see som
http://msdn.microsoft.com/en-us/library/bb204770(VS.85).aspx#no_selfreg
http://msdn.microsoft.com/en-us/library/aa371608.aspx
As Phil recommends, use heat.exe to extract the COM registration
information from your DLL's and/or OCX's. It is very good at doing this
& the generated code should need on
I use devenv.exe in my build script to build a solution with my 5 WiX
projects regularly. I'm using VS 2005 with the latest WiX 3.0 toolset
(currently v3.0.5210.0, I update generally every time a new build is
posted on the RSS feed).
Have you tried looking at the error log when you build? Try pipi
The text in the Description attribute is what is displayed for the
tooltip to the best of my knowledge.
Change it from "$(var.ProductName)" to "[INSTALLDIR]" and it should in
theory work but you may need to use a public property (e.g. TOOLTIPDIR)
and set it to INSTALLDIR using a Type 51 CustomActio
u
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, April 16, 2009 6:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Fails to register a dll that depends on VC9
runtime
http://msdn.microsoft.com/en-us/library/bb
Use , works fine for me doing exactly what you're trying to.
Better still use heat.exe to generate your Fragments & it'll save you
time. Heat.exe is the WiX 3.0 replacement for tallow.exe.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://msdn.microsoft.com/en-us/library/aa367593(VS.85).aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scot
Handle your MSI running with reduced UI levels properly?
http://msdn.microsoft.com/en-us/library/aa372391.aspx
When you uninstall using Add/Remove programs the MSI is run with the /qb
flag to the best of my knowledge (it certainly looks the same as when
you run "msiexec /x /qb").
It sounds like s
It's possible to register DLL's by using heat.exe to harvest the
self-registration information & outputting a fragment to add to your
project. Heat.exe has a page in the WiX.chm under "Tools and Concepts"
and by running it with the /? Flag it gives plenty of information on how
to use it to get the
One of the regular list posters, Neil Sleighholm, has a pretty good blog
post on how to customise the WiX UI standard libraries at
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
without any need to compile a DLL. All your authoring is done in a
Fragment (or multiple fragmen
See this blog post by one of the list posters, Neil Sleightholm. It
should point you in the right direction to achieve what you are trying
to do ->
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Good luck.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (
http://msdn.microsoft.com/en-us/library/aa370905.aspx#date__time_properties
Short answer: no.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solut
http://blogs.msdn.com/robmen/archive/2006/05/30/610950.aspx
Short answer: you can't.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Lim
w pointed lines.
The property 'INSTALL_FILE' is not getting set here.
Basically what I want to do is storing this property value in registry
and then take appropriate action while running my application exe.
Why not use the Merge element & MergeRef element as they were intended?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registe
I have the following in one of our products:
I get no warnings at all when building that product's project. However I
am using WiX v3.0.5217.0 while it appears from the original post that
Riyaz is using WiX 2.0 so it could be something that was removed in the
v3.0 light code throwing the w
They don't handle patching very well either. The Welcome Dialog refers
to a Resumed install when running a patch (MSP) and the Progress Dialog
is devoid of all text except the ActionText. Exit Dialog could probably
do with more specific text to Patching too.
Unfortunately the WiX extensions soluti
http://msdn.microsoft.com/en-us/library/aa372096.aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
1. The web stuff I'm not sure about. It's likely possible using custom
actions as with most things. Someone else may have tried something
similar but I don't think pulling arbitrary files off a web server is
supported by default in the Windows Installer.
2. Very possible using standard Windows Ins
x and if it's a /passive
uninstall I don't want to display anything.
Pally Sandher wrote:
>
> http://msdn.microsoft.com/en-us/library/aa372096.aspx
>
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141
I suggest you use a more 'unique' name than "help.chm" though.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integr
I've created patches which do exactly what you're trying to do but from
your description I can't pinpoint where you're going wrong.
If you could post the .wxs file you're using to create your .pcp file, I
or someone else on the list should be able to help point you in the
right direction.
Cheers,
I just updated to v3.0.5301.0 (was using v3.0.5224.0 last week, I update
when a new build is posted on the feed).
I tried building a .wixproj with Votive (We use Visual Studio 2005 at
present) which built perfectly fine yesterday during the automated build
I have my machine do every morning. Now it
I did the same. Works completely fine.
Started WinXP SP3 VM.
Installed Visual Studio 2008 Shell (integrated mode)
Installed WiX v3.0.5308.0
Launched Visual Studio 2008 IDE from shortcut on Start menu.
Clicked the "Create Project" link on the Start Page & I can see the WiX
project types.
Clicking
http://msdn.microsoft.com/en-us/library/aa368585.aspx
http://msdn.microsoft.com/en-us/library/aa369536.aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Envi
Why isn't it intuitive? I use it for the Visual Studio Redistributables
& it feels completely fine to me but then I've created Merge modules for
partner companies to distribute our software in the past so I've seen it
from both sides of the MSM so to speak.
A merge module is a collection of compone
database.
MergeGroup's would be a way to better express your intention in the WiX
source code.
Pally Sandher wrote:
>
> Why isn't it intuitive? I use it for the Visual Studio
> Redistributables & it feels completely fine to me but then I've
> created Merge module
1 - Look up RegistryKey and RegistryValue in the WiX.chm. You could get
tallow.exe from WiX 2.0 and use it to parse your .reg file into a .wxs
then use WiXCop.exe on the .wxs to update it to the WiX 3.0 schema.
Heat.exe should be able to do this all in one step since it's the
replacement for tallow
Try:
Works fine for me using CAQuietExec but I use Type 34 Custom Actions where
you're using Type 2. http://msdn.microsoft.com/en-us/library/aa372048.aspx
Also InstallDir is more than likely a public property. Case matters.
http://msdn.microsoft.com/en-us/library/aa370912.aspx
You may want t
Might be possible using a custom UninstallString in the registry.
http://msdn.microsoft.com/en-us/library/aa372105.aspx
How you would overwrite the generated one (msiexec /x [ProductCode])
written during the install process is a good question though. Might be
possible using a Custom Action schedule
WiX has nothing to do with uninstalling anything.
The Windows Installer however uninstalls anything specified in the
REMOVE property http://msdn.microsoft.com/en-us/library/aa371194.aspx
As far as I know Component Conditions only affect Install not Uninstall
http://msdn.microsoft.com/en-us/library
The warning thrown by candle is saying you should add an Upgrade
attribute to your product tag. It is simply Upgrade="" with a GUID
inside the quotes.
With regards to the 3 light errors, see the section in the WiX.chm "How
To: Create a Shortcut on the Start Menu" as they're all related to your
sho
I think you may be too late to directly reference a file using
[#filekey]. The WiXShellExec example at
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
uses a [#filekey] value in the WiXShellExecTarget Property so it should
be fine if you do something similar.
http://msdn.micros
Plus the Windows Installer Reference is also accessible through a web
browser on MSDN at http://msdn.microsoft.com/en-us/library/aa372860.aspx
Stoney see Feature Table ->
http://msdn.microsoft.com/en-us/library/aa368585.aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141
You can use the -dr option to set the DirectoryRef automatically for you
(and you probably want to use the -cg option to generate a
ComponentGroup for you to use in your Feature as when your components
change, they're not going to be installed by your installer if they're
not specified in a Feature
Try the following:
1
It should then be enabled if the passwords match or if the ComboBox has
a value selected but disabled otherwise. If you only want it to be
enabled only when the passwords match and the ComboBox has a value
selected, change the "OR" in the condition to "AND".
Good lu
Check the language entry on the .exe file.
If it doesn't exist in the "Decimal value" column in this list
http://msdn.microsoft.com/en-us/library/0h88fahh.aspx it's not valid & is
causing the error.
Again follow Peter's instructions to fix it.
Palbinder Sandher
Software Deployment & IT Adminis
Until today I was using 3.0.4401.0 in Visual Studio 2005 without any
problems since it's release at the start of the month.
I suggest you guys try installing 3.0.4415.0 from
http://wix.sourceforge.net/releases/3.0.4415.0/ as I upgraded to that
release this morning with no issues either.
I use XP6
Your inner text looks fine. I use the same but inside a CDATA tag e.g.
I would try that & see if it fixes your uninstall problem. No idea why
it would but you never know. I put my inner text inside CDATA tags as a
habit even when it shouldn't be required as in your code. Are you sure
the error i
http://www.tramontana.co.hu/wix/
Little old now but it should set you on the right track.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental S
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Tutorial WIX Edit
Thank you very much for your fast respond, in this tutorial they don't
use WIX Edit. Is there samples?
2008/8/27 Pally Sandher <[EMAIL PROTECTED]>
> http://www.tramontana.co.hu/wix/
>
> Li
I'd blame infrequent usage. The only time I've had to "relearn" anything
with regards to WiX is when I switched from using v2.0 to using v3.0 &
even then I only had to "unlearn" the bad habits v2.0 imposes upon you
which are no longer necessary in v3.0. The v3.0 help file is more than
adequate for
Look under "Advanced WiX Topics" in the WiX 3.0 documentation. Should be
a subcategory called "WiXUI Dialog Sets". If you're using Votive have a
quick look at the "Extensions" sections specifically "Using WiX
Extensions" page as you're likely to get an error if you try to build
your MSI without add
Modify your Feature as follows:
That should work as you expect it to.
ComponentGroupRef's are no different to ComponentRef's inside Feature
tags. Your use of Fragments is also fine.
The problem is that your Condition was setting the Level of the Feature
to 0 when the condition e
There's no need to resolve the environment variable to use that
location.
Use
<--insert your code here-->
http://msdn.microsoft.com/en-us/library/aa372057.aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.co
http://msdn.microsoft.com/en-us/library/aa371101(VS.85).aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered
WiX 3.0 does have 2-3 lines of code to implement this.
WiX 2.0 doesn't.
In WiX 3.0 I would do it thus:
WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 AND
(Installed AND NOT REINSTALL)
http://www.iesve.com/"; />
Which would add a checkbox on the ExitDialog when Uninstallin
>But when I try to uninstall I get the message:
>Product: Testing setups -- Error 1321. The Installer has insufficient
privileges to modify this file: J:\TestingSetups\MsSql\TestDb.mdf.
>Does anyone know a way to get around this?
Have you looked at a full log of the uninstall process?
Sounds to m
Subject: Re: [WiX-users] Problem with conditional install
You basically just offered up the inverse of what I suggested.
On Mon, Sep 1, 2008 at 5:41 AM, Pally Sandher
<[EMAIL PROTECTED]>wrote:
> Modify your Feature as follows:
>
> AllowAdvertise="no" Display="hidden
You could create your own Custom UI set with your different sized
bitmaps using WiXUI rather than recompile the DLL.
Then you could specify it in your Product as you would the stock UI sets
e.g.
Download the WiX Source, extract it & browse to
\src\ext\UIExtension\wixlib\
All the UI .wxs files are
Does anyone know why util:InternetShorcut creates a .lnk rather than a
.url? My current code for creating a web link on the start menu is as
follows:
...
http://www.iesve.com"; />
...
The shortcut it creates ends up with the first indexed icon from
I had to do a similar thing recently due to a plug-in we'd outsourced
for development. It is possible to do in MSI but as Bob says it will
only work for the user running the uninstall which for your average
non-commercial user is fine but it's liable not to work for everyone
else as the user instal
Bob Arnson wrote:
>Robert O'Brien wrote:
>> q2 - do the same REINSTALLMODE switch settings apply when trying to
use a patch to carry out a minor or major upgrade?
>
>Yes, though usually MSI picks the right values for you. Though patches
aren't generally double-click installable; you usually need
The MSI only does what you tell it to do. I had the same issue when I
created my first MSP.
You need to modify your code that generates dummy1.msi so that all the
files you're removing have RemoveFile tags specified for them. Simply
deleting the File tags from your code isn't enough (I find it mor
Change it from "ignore" to "check" as it says in the documentation for
the CustomAction tag.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental S
Sounds like it could be an issue with a service on Vista. Most likely to be
something to do with indexing or searching. I'm not 100% up to speed with all
the new features in Vista but I might see if our releases also exhibit this
behaviour. Our Vista Virtual Machines have SP1 applied though whic
Value="dir" means nothing. This is why it is failing.
What are you trying to get it to run?
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environment
You have no inner text set for your CustomActions so they will always
execute whenever the MSI is run (install, repair/upgrade & uninstall).
Use Installed AND NOT REINSTALL to
make it run only during uninstallation. If you only had 'Installed' in
the inner text it would also run during repair/upgr
As stated before Value="notepad.exe" & Value="psexec.exe \\192.168.1.2
-c WebsiteInstall.exe" mean nothing to the Windows Installer which is
why your installation fails.
Value="C:\Windows\notepad.exe" might give you better results.
Palbinder Sandher
Software Deployment and IT Administrator
T: +
Add Indirect="yes" to the Edit box control.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC
There's a "How To:" in the WiX 3.0 documentation which describes how to
create shortcuts without any problems.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrat
1. As Bob says on the post you linked, you need to write a chainer for
this functionality as it is not supported by the Windows Installer.
2.
...
3. It depends on your upgrade. I've released 1.0, 1.1 & 1.2 MSI's of one
of our releases all of which upgrade fine using correctly authored
Upg
You can use Conditions on your Features to set the Level.
e.g.
If you ran your MSI as "msiexec /i myproduct.msi INSTALLELEVEL=2000
ONLYB=true" it would only install Feature B as Feature A would have it's
Level set to since the public Property ONLYB has a value assigned
http://msdn.microsoft.com/en-us/library/aa367830%28VS.85%29.aspx
WiX & Windows Installer are not the same thing. I think I should just
add this to my signature as the number of times I've pointed this out
just this week on this list is ridiculous.
Palbinder Sandher
Software Deployment and IT Ad
http://msdn.microsoft.com/en-us/library/aa370912%28VS.85%29.aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registere
Your second try is almost correct. You need to add the following to your
code however:
Otherwise, as you've noticed, the existing version is not uninstalled
before the new one is installed.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
In the WiX 3.0 documentation under the "How To Guides" section there is
a page on creating shortcuts. This works fine without any ICE validation
errors or warnings even when ALLUSERS=1 is set.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 9
I have the exact same problem with a Out-Of-Process COM server & it
would be absolutely awesome if heat.exe would be able to process these
in the same manner as it does for DLL's & OCX's which have a
DLLRegisterServer entrypoint but I doubt that'll ever happen. I'd much
prefer having the fragment f
I'm trying to use util:XMLFile to modify the inner text of a tag in an XML file
during installation which is installed by my MSI for one of our plug-ins.
The XML file is named IESveInterfaceParameters.xml and contains the following
code:
M:\IES\apps
My installer code is as follow
I have the same problem trying to modify the inner text of a node.
My code looks like the following:
...
...
The contents of the IESveInterfaceParameters.xml file are as follows:
M:\IES\apps
And I get the same result in my log file:
Action 12:08:28: ExecXmlFile.
MSI
nsion?
I'd recommend using XmlConfig instead of XmlFile. The following should achieve
what you want:
This blog post has some more examples of using XmlConfig:
http://blogs.msdn.com/gisenberg/archive/2007/10/09/wix-v3-and-xmlconfig-xmlfile-troubleshooting.aspx
##
$
The WiX 3.0 documentation has a page named "Adding Custom Actions" in
the Advanced WiX Topics section which describes this exact situation
albeit using a DLL EntryPoint rather than a .exe but it's not rocket
surgery to figure out how to modify it to suit your needs.
Palbinder Sandher
Software De
heat.exe file -gg -nologo -out
Substitute with your DLL filename & with something
you like (I tend to use the name of the DLL or OCX but with .wxs
instead).
That should generate you a Fragment with the DLL in a File tag & all the
registration which DllRegisterServer would do. Make sure you ch
Just format the text in your controls as you would in a text document.
e.g.
http://msdn.microsoft.com/en-us/library/aa372076%28VS.85%29.aspx
(it says to use multiple one-line text controls located below each other
but the above works fine for me).
Palbinder Sandher
Software Deployment and
IT
http://msdn.microsoft.com/en-us/library/aa367592%28VS.85%29.aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Register
1 - Yes it is the correct way but fix your order tags & the src tag is
deprecated, use SourceFile instead. If you have one TargetImage your
patch will only update that version & nothing else.
2 - This is a mailing list where people voluntarily offer their help.
Sending a "bump" 40 minutes after
Yes but you will get an ICE80 error when compiling if you set
Win64="yes" on a component when your MSI is an x86 build & vice-versa.
Why would you want to?
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**De
It must be possible as all WiXUI have an optional checkbox on the
ExitDialog which runs a ShellExec Custom Action if checked. Have you
looked at using this instead of authoring a separate dialog? In the
documentation look under the "How To Guides Section". The page title is
"How To: Run the Install
Just create a Launch Condition with "VersionNT64 AND Intel64" as the
inner text.
http://msdn.microsoft.com/en-us/library/aa372497(VS.85).aspx &
http://msdn.microsoft.com/en-us/library/aa369553(VS.85).aspx
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +
lude those components in your 32 bit
>> installer, or alternately, don't offer a 32 bit installer. In some
>> corporate environments, that might work.
>>
>> Chris
>>
>> On Tue, Oct 28, 2008 at 9:19 AM, Michael Owings
<[EMAIL PROTECTED]> [EMAIL PROTECT
I know there is a long-winded way of doing this which bloats my MSI by
having duplicates of the files in it but I was wondering if there's any
easier/cleaner way of achieving the same thing.
Basically I have 2 directories which are set by RegistrySearch
Properties which, depending on whether the R
http://msdn.microsoft.com/library/aa370308.aspx &
http://msdn.microsoft.com/en-gb/library/aa370842(VS.85).aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environme
1 - update your compiler to the latest.
2 - read the topics on Patch building in the WiX help. They are under
"Advanced WiX Topics".
3 - don't double post to the list.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**De
I'm using the x64 MSI's to install the WiX toolset & compiling using the
Visual Studio 2005 IDE (yes I have ProjectAggregator2.msi installed).
I installed v3.0.4707.0 yesterday. Built my solution which has 5 WiX
projects in it. I get no errors but there are no MSI's built.
I've tried uninstalling
ndows Installer XML toolset.
Subject: Re: [WiX-users] v3.0.4707.0 doesn't work.
Pally Sandher wrote:
> I installed v3.0.4707.0 yesterday. Built my solution which has 5 WiX
> projects in it. I get no errors but there are no MSI's built.
>
Have you tried a comm
following two condition statements differ from an MSI
perspective? Only the second method works in this case.
1. NOT
Intel64 2.
Could anyone please clarify??
Pally Sandher wrote:
>
> Just create a Launch Condition with "VersionNT64 AND Intel64" as the
> in
You can have as many QtExec Properties as you like. All you need to do
is create a Property with your command in the Value which is named the
same as the Id of the QtExec CustomAction as is described in the "Quiet
Execution Custom Action" page in the WiX documentation (it's under
"Standard Custom A
http://msdn.microsoft.com/en-us/library/aa367559.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151
I use:
Which works fine for us as far as I know.
Try using the CDATA tag for the condition & get the user to test it
again.
Also if you only want it to install on the 32-bit versions XP & Vista,
you should modify your condition to something like
The brackets may not be strictly necessary
901 - 1000 of 1015 matches
Mail list logo