Ok , I use a preprocessor extension and looks like it is working
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-access-BootstrapperApplicationdata-xml-from-wix-extension-tp7592877p7592907.html
Sent from the wix-users mailing list archive
Ha sorry I solve other issue
my problem is that I need to get the Directory name out of the MSI if the
directory is a configurable directory
the manifest only contain the directory ID
I need the name to be able to show the default path for a feature
the problem is that the path for the MSI
I already posted a related problem here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-command-line-not-effective-td7592884.html
and
http://stackoverflow.com/questions/21989084/wix-managed-ba-command-line-not-effective,
which is about command line passed during upgrade.
Thanks Bob, It is working. I have another one doubt, how can we get the
downloading package name. I should show the downloading msi package name in
UI. I have created a custom BA. In which Event i will get the acquiring
package name?
Thanks,
Saravana
--
View this message in context:
Hi All,
I am using Wix 3.7. I have created custom bootstrapper application for
creating web installer setup. It downloads and install the MSI file from
server. MSI file installation is started once download complete. I am not
facing any problem with this operations.
I have some doubts in
Actually it turns out that it is not actually working. It was working' in
the sense that the above changes allowed the Compiler Extension project to
compile succesfully. However in a nost project, if the compiler encounters
any message related to this XML file it throws the following exception.
Hi!
If you're using TestBA written by bryan, you'll have to manually interpret
your parameters.
You'll have to implement what the BA will do when these are passed.
The results you see from your other post is correct. Since you don't have
the implementation, it won't run the uninstall.
Go
You can't run a merge module or install it as a standalone item.
Merge modules must be used at build time when an MSI file is being
created. That's what the merge term is about.
You can ship merge modules (like Microsoft does) so they can be
included in the MSI files that users of their products
Hi UG,
I tried to implement a complex bootstrapper installer - unfortunately I made a
mistake:
My Bundle consists of one msi package. The installation was successful. After
installing I wanted to implement the uninstall routines. But my
debug-bootstrapper do not want to recognize the
Thank you Bob for the link to the blog.
In general I agree with Rob that we should consider Bundle as if it is MSI,
which is cached and manageable. That is perhaps also the reason why
setupexe/setupbld is retired after WiX 3.5.
Typically when we author a Bundle to install one or more
n the Product.wxs, I set Schedule=afterInstallInitialize in the
MajorUpgrade so that if the installation fails, it will roll back to the
previous version.
Our Windows Service uses app.config that the installer copied to the
installed machine. We do this by including the below line in the
Have a read of this:
http://msdn.microsoft.com/en-us/library/aa370531(v=vs.85).aspx
Now, before you do your upgrade, have a look at the file's modified and
creation dates. If they match, then MSI takes that as a signal that they
can be overwritten (because it sets those dates to the same value
Thank you for your reply.
The first installation was today, so the app.config file date is today's
date.
I then today modified the app.config file on the installed folder.
Do I understand it correctly that
1. when I re-install again today, it overrides the app.config file because
the dates of
--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
It's date a time, not just date.
-Original Message-
From: faujong [mailto:fiefie.ni...@gmail.com]
Sent: Tuesday, February 25, 2014 3:16 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to not copy a file in subsequent installations?
Thank you for your reply.
The
If that's the case, then why when I re-install today, it overrides the
app.config, even though the time of the app.config in the installer and on the
installed folder is different ?
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, February 25,
Yes, what you said make sense. The suggestion would be to remove the custom
actions that create the SKU Product ARP entry and just let Burn do it. It ends
up being the same thing in the end except you need one less custom action
(always a good thing!).
Hi,
I am not sure if I can do this but...
I have created a web site using the WIX
IIS::WebAppPool/IIS::WebSite/IIS::WebServiceExtension/IIS::WebDir
I would like to know if there is a way NOT to remove the website during an
upgrade? (major upgrade, does an uninstall then install...)
thanks,
Make the Component permanent.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Tuesday, February 25, 2014
Then how does it get removed on an Uninstall?
From: Rob Mensching-7 [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7592936...@n2.nabble.com]
Sent: February-25-14 5:10 PM
To: Steven Ogilvie
Subject: Re: how to keep a web site during upgrade...
Make the Component permanent.
Then how do you uninstall it?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-keep-a-web-site-during-upgrade-tp7592935p7592937.html
Sent from the wix-users mailing list archive at Nabble.com.
Sorry, I missed the implied statement that you wanted uninstall to uninstall as
well. It won't. What you're asking for is a very complex feature request that
we've seen across the whole board of Windows Installer behaviors. The Windows
Installer doesn't make this easy (maybe not possible in
Thank you Rob!
Unfortunately, the MSIs and MSPs in our product are already authored this way
as I described in my last email, that they themselves manage SKU ARP entries.
And it is costly to update our MSIs and MSPs to remove such custom actions, and
switch our custom bootstrapper to Burn with
What are the exact options you are using when reinstalling? (You can pass nasty
options to msiexec to have it force overwrite things.) A verbose install log
will tell you exactly why it's doing it.
-Original Message-
From: Fiefie Niles [mailto:fiefie.ni...@nadex.com]
Sent: Tuesday,
Where can I get the verbose install log from ?
Sent via the Samsung Galaxy S™III, an ATT 4G LTE smartphone
Original message
From: Hoover, Jacob jacob.hoo...@greenheck.com
Date:02/25/2014 5:12 PM (GMT-06:00)
To: General discussion about the WiX toolset.
Follow the instructions here:
http://support.microsoft.com/kb/223300
The simplest way for logging a single session is to start the installer
with the /l switch
msiexec /i c:\path\to\myinstall.msi /l*v c:\path\to\myinstall.log
On 25 February 2014 23:56, fiefie.niles fiefie.ni...@gmail.com
26 matches
Mail list logo
