Thanks, that was it. I have been calling both actions (install and uninstall)
all the time. Now i do not call install when it's desired to uninstall the
product. The bundle entry is getting removed from ARP :) .
--
View this message in context:
Hey everyone,
I've got a large number of directories and files that look like this (pseudo
code):
DirectoryRef Id=INSTALLFOLDER
Directory Id=XXX_FR
Component Id=XXX_FR
file Name=myapp_fr.exe
Source=!(bindpath.start)/myapp_fr.exe keypath=true/
Can anyone say what the current state of the Update element that goes into a
Bundle is?
http://wixtoolset.org/documentation/manual/v3/xsd/wix/update.html
Does it work, currently, with the standard BA? Or would someone have to
write their own to take advantage of detecting an updating MSI package
1) Yes
2) Public Properties (those that can be altered on the command line and/or
(with the Secure attribute) will pass to/from the UI and Execute sequences MUST
be all upper case.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
In 3.9, only the engine was updated to support it. I have a fork with a working
WixStdBA that implements what I needed to get updates working, but I've not
gotten it reviewed nor submitted for 3.10 as of yet. I believe
https://github.com/jchoover/wix3/tree/develop-3.9-WixStdBA would give you a
Thanks Jacob, that sounds like really good work on your part. I will follow
the link to learn more about it, and it will be nice to eventually see that
in the standard BA.
--
View this message in context:
Thank you for your fast response, John.
Now the next question.
I have a pattern below. The language however is really derived from the locale
(ex. en-US, fr-FR, etc.). I pull the Language out in a CA and each component
has a ConditionalLANGUAGE=en/Conditional inside of it.
I would like to
No, but it would have to qualify as one of the easier ones to write.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original
It would behove me to ask if this would be welcome in WiX 4 as a new feature or
should I just have it be another custom extension function that we have for our
in-house development?
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
I am trying to run a CA after setting up a website to modify the web.config
file based on the IIS version being used.
What should I use for the After value (in the InstallExecuteSequence) to
make sure the CustomAction executes after the website is installed?
Here is the code I am using:
Why are you re-inventing the wheel? Util:XmlFile and Util:XmlConfig are quite
serviceable and give you full rollback support.
Scheduling depends. There's no one magic value. Since you should be using a
deferred action, you'll be limited to the range after CostFinalize to before
Hello,
When I try and install my MSI on XP I get an error code 2260. I works
just fine on Windows 7 and 8. Any ideas?
From the msiexec log:
MSI (s) (44:DC) [19:13:57:281]: Executing op:
ActionStart(Name=RegisterProduct,Description=Registering
product,Template=[1])
Action 19:13:57:
What version of Windows Installer Service is installed on the XP box and what
version does the MSI require? Post-Vista generally uses 5.0. XP often has
3.0, although it can be upgraded to 4.5.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
On 21/10/14 22:18, John Cooper wrote:
What version of Windows Installer Service is installed on the XP box and what
version does the MSI require? Post-Vista generally uses 5.0. XP often has
3.0, although it can be upgraded to 4.5.
Hmmm ... msiexec says 3.0. I installed 4.5 and got exactly
What Version of WiX are you using and if your App uses the .Net
Framework, what version is that?
Quoting Christopher Fraser chr...@goop.org:
On 21/10/14 22:18, John Cooper wrote:
What version of Windows Installer Service is installed on the XP
box and what version does the MSI require?
I'm using WiX 3.8 and I don't use .Net (in this, at least).
On 21/10/14 23:09, Carter Young wrote:
What Version of WiX are you using and if your App uses the .Net
Framework, what version is that?
Quoting Christopher Fraser chr...@goop.org:
On 21/10/14 22:18, John Cooper wrote:
What version
Hello, first time question:
I am trying to limit my application to Windows Vista and 7, and want it to
be removed by the OS during an upgrade to higher OS. Is this even possible?
Is marking Condition with versionNT enough for this, or is there another
condition that needs to be set?
I have run my installers on xp with that version number of 200 and it was
fine.
XP w/ SP3
Someone correct me if I am wrong but shouldn't both of these be unique?
(I'm not saying this is the problem.)
?define ProductCode=b61f9010-3474-11e4-8c21-0800200c9a66 ?
?define
You didn't happen to have it open in orca when you ran the installer did
you?
On Tue, Oct 21, 2014 at 5:14 PM, Christopher Fraser chr...@goop.org wrote:
I'm using WiX 3.8 and I don't use .Net (in this, at least).
On 21/10/14 23:09, Carter Young wrote:
What Version of WiX are you using and
If a customer upgrades their OS, your Application will stay installed,
and will run in compatibility mode. Upon Uninstall/Reinstall, your
condition will be met and your Application won't install. To see this
functionality in action Download a copy of the Windows Upgrade
Adviser. You'll
Here is the condition you can use
Condition Message=This application is only supported on Windows
Vista, Windows Server 2008, or higher.
![CDATA[Installed OR (VersionNT = 600)]]
/Condition
Hi,
I have an installer that will install either a client only, or both the
client and the server. The way I determine which one to install is by having
a custom ui with two check boxes. A variable is set and checked in the chain
to decide if one or both (client and server) is to be installed.
22 matches
Mail list logo
