x27;t have to set the
neverovewrite.
From: Jeremiahf
Sent: 28 January 2015 16:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Upgrading old installer
So you want to leave the old config file there? Will your new installer
configu
So you want to leave the old config file there? Will your new installer
configure the new config file and maintain it from there on?
On Wed, Jan 28, 2015 at 8:15 AM, Kraygsoft
wrote:
> Anyone
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2
So I have created a nice new installer using WiX for my customer complete
with nice shiny new custom bootstrapper and everyone was happy. Rejoicing in
the death of their old buggy Visual Studio based installer. However I have
struck a problem. There are a number of user configurable config files
i
Anyone
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-old-installer-tp7599052p7599055.html
Sent from the wix-users mailing list archive at Nabble.com.
, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
Sent: Monday, October 27, 2014 14:57
To: 'General discussion about the WiX toolset.'
Subject: Re: [WiX-users] Upgrading Burn bootstrapper with msi
Windows Installer can remove the bootstrapper for you. Use the Windows
Installer FindRelat
: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading Burn bootstrapper with msi
Hello everyone,
I have a situation where until now I had one bootstrapper chaining several msi
packages, but now I must switch to one msi instead of bootstrapper. The problem
is that msi installer will not
Hello everyone,
I have a situation where until now I had one bootstrapper chaining several msi
packages, but now I must switch to one msi instead of bootstrapper. The problem
is that msi installer will not trigger the upgrade using upgrade code of the
bootstrapper. I have searched through the n
On 28-Jul-14 08:51, Chetan Dabade wrote:
> i scanned my whole machine but couldn't find file "*Common.wxs*" and in
> addition under Installer.wxs file there is a variable declared as:
>
>
> **
> while googling i found the above mentioned error
>
> http://www.joyofsetup.com/2010/05/20/its-time-to-
Hi all,
I found the issue and fixed it. The issue was under each .wixproj file the
value of $(WixToolPath) was referring to older version of Wix (.i.e 3.5)
$(ProgramFiles)\Windows Installer Xml
v3.5\bin\
I re-visited each individual projects unloaded it, edit the .wixproj file
and change the
Hi all,
I am working on task which includes upgrading Visual Studio 2010 to 2013 as
well as upgrading WiX 3.5 to WiX 3.8. I have the basic knowledge of WiX and
i am not the expertise as such.
Conversion of .NET projects were successful, however in case of WiX
projects conversion from 3.5 to 3.8 i
Thanks I have add the "older" MSI's upgrade code to the upgrade table and will
test that tomorrow :)
Cheers,
STeve
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: June-09-14 4:46 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
I do not have direct experience with this issue, but I suspect the thing to
do is to leave the new package name as is, but rather author multiple
upgrade codes to also remove the old product.
http://www.joyofsetup.com/2008/09/07/hint-be-generous-with-upgrade-codes/
--
View this message in conte
what if at build time I change the name of the MSI to be the same as the
original MSI's name and use the same upgrade code?
Would that work ?
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-tp7595079p7595124.html
Sent from the wix
Your Second Option is Best, if not you will have a side by side install
Quoting Steve-Ogilvie :
> I have a quick question...
>
> We released 4.2.0.x about 3 months ago. and our Services MSI was named
> TITUS_Services_Setup_x86 we shipped only the 32 bit services with our Client
> installer with a
I have a quick question...
We released 4.2.0.x about 3 months ago. and our Services MSI was named
TITUS_Services_Setup_x86 we shipped only the 32 bit services with our Client
installer with a different GUID and upgrade code.
now we have changed our Services MSI to TITUS_Client_Services_x86 and
Hey folks,
Hello, was wondering if I could get some thoughts on this...
I've been asked to provide a bundled exe created in burn and a MSI for our
product... The idea being that clients will generally use the exe which will
install the our msi and VSTO.
The standalone MSI I've been asked to pr
ubmit my pull request once the documentation has been updated.
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Monday, May 13, 2013 11:16 AM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-
Everyone,
I have a multiple instance install that I am working on and ran into an issue
doing upgrade testing. It looks like all instances are removed when one of the
instances is upgraded. This looks to be because WIX does not allow for the
UpgradeCode to be modified in the instance element.
Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 28 March 2013 15:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrading an Install fails to downgrade a 3rd party
library
I don't like any of these per say, but just throwing some ideas out for you to
ponder/try.
:24
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrading an Install fails to downgrade a 3rd party
library
You could try scheduling remove existing products earlier, after
InstallInitialize.
-Original Message-
From: Jackson Pope [m
t: Re: [WiX-users] Upgrading an Install fails to downgrade a 3rd party
library
You could try scheduling remove existing products earlier, after
InstallInitialize.
-Original Message-
From: Jackson Pope [mailto:jackson.p...@nonlinear.com]
Sent: Thursday, March 28, 2013 3:28 AM
To: wix-
You could try scheduling remove existing products earlier, after
InstallInitialize.
-Original Message-
From: Jackson Pope [mailto:jackson.p...@nonlinear.com]
Sent: Thursday, March 28, 2013 3:28 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading an Install fails to
Hiya all,
Similar to this question on StackOverflow
(http://stackoverflow.com/questions/4227456/windows-installer-deletes-versioned-file-during-product-upgrade-instead-of-down)
I've got a new version of an install that accesses an old version of a 3rd
party library.
Previous version (1.0) refe
nfig
files - generate them in the application from defaults if they aren't
present.
-Original Message-
From: Benjamin Kaduk [mailto:ka...@mit.edu]
Sent: 19 September 2012 20:04
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] upgrading from 64-bit to 32-bit product leavesfiles
beh
Bob Arnson wrote:
> Benjamin Kaduk wrote:
> > I'm really confused by this behavior, and don't know where to look
> > further.
> The verbose upgrade log. It will tell you why MSI decided to leave a
> ile behind.
The problem is, as far as I can tell from the verbose upgrade log, MSI
does not think
On Tue, Sep 18, 2012 at 8:17 PM, Bob Arnson wrote:
> On 18-Sep-12 16:24, Benjamin Kaduk wrote:
>> I'm really confused by this behavior, and don't know where to look
>> further.
> The verbose upgrade log. It will tell you why MSI decided to leave a
> file behind.
If it decided to do so. It could a
On 18-Sep-12 16:24, Benjamin Kaduk wrote:
> I'm really confused by this behavior, and don't know where to look
> further.
The verbose upgrade log. It will tell you why MSI decided to leave a
file behind.
--
sig://boB
http://joyofsetup.com/
--
Hi all,
I've got a product that has historically been 32-bit only but has since
gained a 64-bit installer. I still have to distribute both 32- and 64-bit
versions (if only to support 32-bit systems as well as 64).
I don't want to allow both a 32-bit and a 64-bit version to be installed
side-by
C++) and Wix's own BA (written in C#) as examples of where
one could start.
Jacob
-Original Message-
From: vchauras [mailto:vivekchauras...@gmail.com]
Sent: Friday, September 07, 2012 5:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading to Burn [list of steps
Hello all,
We already have a big size msi for our product and it supports installation
of various features. Now, with Wix3.6 onwards, we want to use Burn in our
build stage.
My main concern before moving to Burn is that :
- how would I know if my current MSI needs Burn supported functionality or
On Wed, Sep 14, 2011 at 7:46 PM, Bob Arnson wrote:
> On 14-Sep-11 19:12, Daniel Pratt wrote:
> > uninstall mode. I've tried many different permutations of command lines,
> but
> > the typical error message is "Invalid command line argument. Consult the
> > Windows Installer SDK for detailed comm
On 14-Sep-11 19:12, Daniel Pratt wrote:
> uninstall mode. I've tried many different permutations of command lines, but
> the typical error message is "Invalid command line argument. Consult the
> Windows Installer SDK for detailed command line help".
>
> Now I suppose that this error message is tr
have solved the different issues that come up.
Michael
-Original Message-
From: Daniel Pratt [mailto:colorblind...@gmail.com]
Sent: Thursday, 15 September 2011 9:12 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Upgrading one of multiple installed
This post is a follow-up to my previous post(s) in this forum, wherein I've
been trying to figure out a way to reliably upgrade a single instance of a
multiple-instance installation. I had determined to try again to set up the
installation to do a "major upgrade", but it appears I have failed (agai
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 15 January 2011 13:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] upgrading custom actions to be data driven
Before I begin describing how to refactor hard wired custom actions to data
d
opher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Sean Farrow
To: "wix-users@lists.sourceforge.net"
Sent: Sat, January 15, 2011 5:02:12 AM
Subject: [WiX-u
Hi:
I'm currently in the process of upgrading my custom actions to be data driven.
In the current implementation of the msi I'm using properties to enable/disable
feature visibility.
Is there a way to do this from a table given that what was about 30 properties
are now going to be entries in a cu
discussion for Windows Installer XML toolset.
Onderwerp: Re: [WiX-users] Upgrading wixproj
Unfortunately, no.
That build was a (now very old) intermediate release. We don't save
intermediate releases for very long. We don't have the resources to
support
drops at all points in t
Unfortunately, no.
That build was a (now very old) intermediate release. We don't save
intermediate releases for very long. We don't have the resources to support
drops at all points in time of the development cycle. If you're using the
the "development branch" of the WiX toolset (which both WiX v
Thanks Rob,
I'd like to avoid having to upgrade all our projects at this time. Is
there a version at http://wix.sf.net/releases that will work with my
\Microsoft\WiX\v3.5\Wix2010.targets style wix projects?
-Eric
On Wed, Jan 5, 2011 at 2:31 AM, Rob Mensching wrote:
> And to answer the actual
Yes, we switched to "v3.x" in hopes that the VS project system will not have
an upgrade in WiX v3.6 and later.
There were a great many changes in VS2010 that caused the project system
upgrade. It's painful and hopefully we've done the work necessary to not
need another one for the life of WiX v3.x
And to answer the actual question, I think 3.5.1419 has rolled off. That
build is almost a year out of date, we don't keep development builds around
for more than a few months typically (and less when we get to Escrow like
with WiX v3.5).
On Tue, Jan 4, 2011 at 11:30 PM, Rob Mensching wrote:
> W
Weekly release are at http://wix.sf.net/releases. Yes, I know, we need to
clean all this stuff up. Sorry.
Eventually http://wixtoolset.org will have all the information.
On Tue, Jan 4, 2011 at 2:14 PM, Eric Goforth wrote:
> Hmmm, I'm on codeplex (http://wix.codeplex.com/releases/view/44406)
>
Hmmm, I'm on codeplex (http://wix.codeplex.com/releases/view/44406)
right now and I don't see a way to download 3.5.1419, is it possible
to do that? I checked out http://wixtoolset.org/ too, but it looks
like that's just a place-holder site for now.
-Eric
On Tue, Jan 4, 2011 at 5:03 PM, Eric Gof
Thanks, it looks like he has 3.5.1419, I have 3.5.2415.
On Tue, Jan 4, 2011 at 4:40 PM, jhennessey wrote:
>
> All builds will say "Windows Installer XML Toolset 3.5" but you need to check
> the actual build version (I think the latest is 3.5.2430.0).
>
> v3.x\Wix.targets is what is current
> --
>
All builds will say "Windows Installer XML Toolset 3.5" but you need to check
the actual build version (I think the latest is 3.5.2430.0).
v3.x\Wix.targets is what is current
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-wixproj-tp58900
Hello,
I looked at the other developer's add/remove programs, it showed the
same version as mine:
Windows Installer XML Toolset 3.5
Before the "upgrade," I see:
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.5\Wix2010.targets
In the .wixproj file, after the "upgrade," I see:
$(MSBuildExtensionsPat
It looks like they have an older version of 3.5 installed than you do. I
believe it used to v3.5 but was later switched to use v3.x. If you both
install the same version it should solve your problem.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/U
Hello,
I have installed Windows Installer XML Toolset 3.5 on my development
machine, which is running Vista 32-bit, for what it's worth. I'm then
opening a .wixproj file using Visual Studio 2010 that was created by a
different developer here using WIX3.5/VS2010, I believe.
At any rate, when I op
sts.sourceforge.net
> Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
>
> Hi,
>
> I changed my approach a little bit. For reference:
>
> This is what I added to my wxs file:
>
> DllEntry='CheckSpecialist' />
>
>
>
[mailto:lukasha...@gmx.at]
Sent: 26 July 2010 11:44
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
Hi,
I changed my approach a little bit. For reference:
This is what I added to my wxs file:
And this is my small CheckSpecialist.c
riginal Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Wednesday, July 21, 2010 4:20 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Upgrading from other setup program to WiX/MSI
>
> Hi,
>
> Today I began creating my first WiX project.
x.at]
> Sent: Sunday, July 25, 2010 5:18 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
>
> Dear Blair,
>
> Thank you for the hint! I will replace my MessageBox-call prompt with
> MsiProcessMessage/WcaProcessM
l executable somehow/somewhere.
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Sunday, July 25, 2010 5:18 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
Dear Blair,
Thank you for the hint! I will replace my Me
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Thursday, July 22, 2010 12:47 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
>
> Dear Blair,
>
> Am 22.07.2010 01:04, schrieb Blair:
>> 1. You can b
al Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Wednesday, July 21, 2010 4:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading from other setup program to WiX/MSI
Hi,
Today I began creating my first WiX project. Until now I used
SetupSpecialist but as I am faci
M
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading from other setup program to WiX/MSI
Dear Blair,
Am 22.07.2010 01:04, schrieb Blair:
> 1. You can build MSIs with WiX that don't require running the setup as
> administrator. Nothing that can be done outside of Windows Installer
wi
Dear Blair,
Am 22.07.2010 01:04, schrieb Blair:
> 1. You can build MSIs with WiX that don't require running the setup as
> administrator. Nothing that can be done outside of Windows Installer without
> elevation requires elevation in Windows Installer to also do.
In fact this is exactly what I do
M
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading from other setup program to WiX/MSI
Hi,
Today I began creating my first WiX project. Until now I used
SetupSpecialist but as I am facing serious problems with it I want to
use WiX in future.
This is my first big question: On clients' com
Hi,
Today I began creating my first WiX project. Until now I used
SetupSpecialist but as I am facing serious problems with it I want to
use WiX in future.
This is my first big question: On clients' computers there will be an
old instance of my program (with SetupSpecialist) installed. Even wor
, November 23, 2009 4:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrading
That's known as a Minor Update but it's only one of the available upgrade
types.
See http://msdn.microsoft.com/en-us/library/aa370579.aspx
Palbinder Sandher
Soft
t: 21 November 2009 10:59
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading
Sorry.. the solution was to execute the msi like this:
msiexec.exe /I product.msi REINSTALL=All REINSTALLMODE=vomus
So I am not stuck anymore.
Regards,
Daniel
Daniel Marjamäki wrote:
>
>
Sorry.. the solution was to execute the msi like this:
msiexec.exe /I product.msi REINSTALL=All REINSTALLMODE=vomus
So I am not stuck anymore.
Regards,
Daniel
Daniel Marjamäki wrote:
>
> I am having trouble with upgrades.
> Upon installation I want to completely uninstall any old versions.
I am having trouble with upgrades.
Upon installation I want to completely uninstall any old versions.
I have seen so many answers about this in various places. But nothing works.
I use the same UpgradeCode in both old and new versions.
I use the same Product Id in both old and new versions.
I u
From: Andy Glass [mailto:agl...@laserfiche.com]
Sent: Thursday, July 23, 2009 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Upgrading to WiX 3, CNDL0005 error.
Greetings all,
I'm working up updating an installer from WiX 2 to WiX3. I've use
Greetings all,
I'm working up updating an installer from WiX 2 to WiX3. I've used WixCop to
do most of the conversion, but I'm getting the following error:
error CNDL0005 : The File element contains an unexpected child element
'util:PerformanceCounter'.
The area in question is:
I have
k.com]
Sent: Wednesday, July 22, 2009 10:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading...
Hello,
I used WIX to create an installer for our last release of our software. I
was using NSIS prior to that, but we had customers who wanted to be to
implement installs over a ne
@lists.sourceforge.net
Subject: [WiX-users] Upgrading...
Hello,
I used WIX to create an installer for our last release of our software.
I was using NSIS prior to that, but we had customers who wanted to be to
implement installs over a network, so we switched. So, we are at a
point where I
Hello,
I used WIX to create an installer for our last release of our software. I
was using NSIS prior to that, but we had customers who wanted to be to
implement installs over a network, so we switched. So, we are at a point
where I have to do another release, and I want to be able to 1) Inst
:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading SQL Server in Wix
Hi Guys,
I wanted to ask the community for any best practices or methods used
with the upgrading of SQL Databases through WIX. The install step is
fine and pretty straight forward, the upgrade process is messy and I am
Hi Guys,
I wanted to ask the community for any best practices or methods used
with the upgrading of SQL Databases through WIX. The install step is
fine and pretty straight forward, the upgrade process is messy and I am
unsure what scripts will run and when. I did a quick search but wasn't
able to
com>
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su...@microsoft.com]
Sent: Thu 02/04/2009 01:40
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading an older version of product
Thanks Phil.
Your have hit the bullseye. You are right. I saw the log
.
Sudripta.
Re: [WiX-users] Upgrading an older version of
product<http://sourceforge.net/mailarchive/message.php?msg_name=5C889913FF236E4190093AF280AB4EC40167E7E295%40wwlkfmail1.wonderware.com>
From: Wilson, Phil - 2009-04-02 00:09
It's nothing to do with the same user account. It&
Sent: Wednesday, April 01, 2009 4:53 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrading an older version of product
The older version hadn't any ALLUSERS value set. The new version has ALLUSERS
set to 1. But, I am installing both the versions from the same user account
Hi
Have you remembered to add "SecureCustomProperties" to your property table?
(Or does candle/light do that for you??)
K.
Yes, I have the following element defined within InstallExecuteSequence of
version 2.0.1000.0.
Another thing is that in the new version of the product, I have comp
n't any 'ARPNOREMOVE' property. The new version hasn't got any of
the property.
Thanks.
Sudripta.
Re: [WiX-users] Upgrading an older version of
product<http://sourceforge.net/mailarchive/message.php?msg_name=5C889913FF236E4190093AF280AB4EC40167E7E22F%40wwlkfmail1.wonderwa
thing is that the product name is
also different in the new version. The only similarity between the two versions
is the upgrade code.
Thanks.
Sudripta.
Re: [WiX-users] Upgrading an older version of
product<http://sourceforge.net/mailarchive/message.php?msg_n
discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Upgrading an older version of product
Do you have a RemoveExistingProducts action defined in your execution sequence?
Jim Williams
-Original Message-
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su..
Do you have a RemoveExistingProducts action defined in your execution sequence?
Jim Williams
-Original Message-
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su...@microsoft.com]
Sent: Wednesday, April 01, 2009 4:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
I have two versions of my MSI... one is version 1.0.0.0 and another is
2.0.1000.0. The upgrade code for both the MSIs are the same. But, there are
many significant differences between version 1.0.0.0 and 2.0.1000.0, including
different install directories and files-to-install. Version 1.0.0.0 in
gt; -Original Message-
> From: Hukumchand Shah [mailto:hukum.s...@gmail.com]
> Sent: 21 March 2009 07:27
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Upgrading ...Not happening
>
> Hi All,
> I want to do upgrade in my current WIX installer
: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Upgrading ...Not happening
Hi All,
I want to do upgrade in my current WIX installer.
I am changing the Version shown below.
and also adding the upgrade element:
But when I make .msi and run it
Hi All,
I want to do upgrade in my current WIX installer.
I am changing the Version shown below.
and also adding the upgrade element:
But when I make .msi and run it by double clicking then it shows error
meaasge attached with mail.
I also checked the log files, it
grade code
draws a line through the products so that the Upgrade table and
FindExistingProducts action can associate them with each other.
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent: Tuesday, January 20, 2009 10:04
To: wix-users
Subject: [WiX-users] Upgradin
I am getting some very odd behaviour when trying to test upgrading my
product.
Up until now I've just uninstalled the previous version before installing
the new version. But now I'm trying to actually upgrade, and what I'm
getting is a little bit baffling.
Just to test the upgrade, I'm only chang
sourceforge.net
Subject: [WiX-users] Upgrading components marked as permanent
Our product includes a TAPI Service Provider (TSP) that requires that it be
installed to System32. I have read that if a file is installed in System32
it should be marked as permanent.
I have made updates to our TSP but the
Our product includes a TAPI Service Provider (TSP) that requires that it be
installed to System32. I have read that if a file is installed in System32
it should be marked as permanent.
I have made updates to our TSP but the installer won't upgrade the version
that is installed. Is there a way to
Hi again, I'm running into trouble when I'm trying to install/remove/install a
patch which applies to multiple versions of a product. Here's a snippet from
the WXS for the patch in question:
(Imagine I'm upgrading product Foo to version C. Version A and B exist in the
wild.)
Craig0ss wrote:
> What about a component search, if it finds the product it fills the
> keypath??
>
Should work. I've never tried it.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
hmmm
What about a component search, if it finds the product it fills the
keypath??
Ive read this but am unsure on how to execute this my self
thanks
Bob Arnson-6 wrote:
>
> Craig0ss wrote:
>> I need my MSI to check for an existing install of the software ie. 5.2.1,
>> now it does this fine
> From: Craig0ss
> Sent: Monday, November 05, 2007 12:01 PM
>
> Ive read alot of other posts regarding upgrading but ive yet
> to find any
> information relavent to my situation, so if anyone knows of
> any threads and
> have the links to them then please post. Here is what i want to do
>
> I n
Craig0ss wrote:
> I need my MSI to check for an existing install of the software ie. 5.2.1,
> now it does this fine, however i also need it to check for the existing
> directory and then pass that information to a variable that the installer
> then sets the installer to install to. Basically i need
Hi guys
Ive read alot of other posts regarding upgrading but ive yet to find any
information relavent to my situation, so if anyone knows of any threads and
have the links to them then please post. Here is what i want to do
I need my MSI to check for an existing install of the software ie. 5.2.1
Mike, Phil -
Thanks for the quick responses !
After some more testing, it appears to be a problem with how InstallShield
is consuming the merge modules ... not with how they're built.
Now I just need to convince another development group to use WiX ...
Regards,
-dmm
--
View this message i
em both in the same component.)
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
DexterSinister
Sent: Monday, April 23, 2007 11:45 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading Publisher Policy Files in Merge Modules
yName table, which you do in WiX by passing the -fv switch to
light.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of DexterSinister
Sent: 23 April 2007 19:45
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrading Publisher Poli
Is there any trick to this ... ?
We've got a merge module that is used by a couple of other groups, and while
the assemblies
get installed to the GAC properly ... when upgraded assemblies & policy
files get shipped, the
policy files don't seem to upgrade properly.
Thanks in advance,
-dmm
--
Vi
at the ICE you put in that field is being passed in as
/sice:64 instead of /sice:ICE64, which is what you want.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Watts
Sent: Sunday, January 28, 2007 12:28 AM
To: wix-users@lists.sourceforge.net
Subje
Hi there,
First of all, Votive v3 and the error messages that come from v3 of
light/etc. are fantastic. That and the mailing list archives allowed me
to answer most of my questions. Kudos!
A few issues/questions remain.
1) I'd like to convert the following to the new RegistryValue wix
eleme
D] *On Behalf Of *Aaron Feng
*Sent:* Thursday, January 04, 2007 07:47
*To:* Bob Arnson; wix-users@lists.sourceforge.net
*Subject:* Re: [WiX-users] Upgrading not doing anything
Bob,
I'm having a lot of problems trying to do minor upgrade. Partly the MSI
is automated using a custom in h
1 - 100 of 114 matches
Mail list logo
