Gladly... here it is. Had to zip it...
Thanks again for trying to help.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5641073/full.zip
full.zip
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SharedDllRefCount-on-Upgrade-tp
Hello wix-users@lists.sourceforge.net,
vijay chander wants to reward you for being his friend! You are
eligible to receive a $1000 dollar Best Buy gift card.
Just follow three simple steps and apply in just a minute. No purchase
necessary.
To see more details and to register to ou
I've been trying for about 12 hours to get Wix project dependencies to work.
Some background, I started with a VS2008/Wix3.0 solution and am upgrading to
VS2010/TFS2010/Wix3.5/MSBuild 4.0.
The old stuff worked perfectly. After upgrading, Wix now appears to totally
ignore Project References and,
Might be better to post the entire log.
Phil Wilson
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Friday, October 15, 2010 12:56 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SharedDllRefCount on Upgrade
Here's two parts of the log... still
Here's two parts of the log... still looking grim...
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5640249/log.txt
log.txt
Thanks for helping out Phil...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SharedDllRefCount-on-U
What does the log say about features being installed, local, absent null etc?
Phil Wilson
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Friday, October 15, 2010 11:03 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SharedDllRefCount on Upgrade
Uh Oh. This doesn't sound good...
Here's what I'm doing to determine if I need to upgrade:
So I am using UpgradeVersion... Is there another way to do what I'd like to
do? (I.e. completely remove the previous version and install a new one over
top?)
Ugh!
--
View thi
It's in the UpgradeVersion element, if you're using that. If "yes" it means
that the features installed in the upgrade will be the same as the ones already
installed. That's Features with an uppercase F, the user visible reconfigurable
pieces of the setup. Those mising components belong to a Fea
It's possible that whitespace isn't being preserved when parsing the content
of the Text element. I don't know if adding xml:preserve attributes (or some
other xml: attribute) will fix that or not.
IIRC what some of us have done for localizing license agreements UI is to do
the following: layout t
Hi,
I have built a managed custom action to check if a UNC path exists. I'm
not installing to this path. This path is simply being set as the value
of a .config file setting during the install. I just want to verify
that it is a valid path. The custom action is defined as follows:
[CustomActi
Thanks for the reply, Phil.
I'm not sure what you mean by "migrating feature states", but these two
components probably don't have the same component names as something in the
previous installer version, and they definitely don't have the same
component guids. But neither do the other componen
Sorry, looks like I posted too soon.
After trying to use SharedDLLRefCount="yes", my WiX installer still won't
install these components.
I should also note that all of the other components have "Action: Local"
... and they get installed.
What's going on here?
--
View this message in context
SharedDllRefCount is intended for co-existence of shared files between non-MSI
and MSI installs. If all the setups that install those files are MSI-based then
don't use SharedDllRefCount. In any case, Windows will automatically increment
it if there is an existing entry for the file location bei
So on an upgrade, I noticed that some important files were not installed. So
I looked in the log and found these:
MSI (s) (7C:28) [12:04:18:128]: Component: Service_Component; Installed:
Absent; Request: Local; Action: Null
MSI (s) (7C:28) [12:04:18:128]: Component: Admin_Component; Installe
All,
What I want to achieve:
I'd like to do a major upgrade with old registry settings retained from
previous installer.
i.e. registry values previously installed by an older installer which
later got updated
I tried the following ways but still failed.
Example:
I have a previous ins
This seems typically a problem of VM configuration.
If you use VMWare, did you check that you setup correctly the VM memory
parameters ?
We had a similar problem, and it was due to ballooning, where RAM is stored on
hard-disk instead of RAM.
Force the VM to use all the reserved memory.
Probably
See
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever
/
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: 15 October 2010 00:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Simple Upgra
Alex,
If you want to do upgrades then you have to use an upgrade code and the
upgrade code must remain the same throughout all your versions.
FindRelatedProducts searches for the upgrade code. If it find one that
matches it knows it's found a related product.
Chris
On 10/14/2010 07:21 PM,
Hi,
Its worth reading the details surrounding installation context
http://msdn.microsoft.com/en-us/library/dd765197(v=VS.85).aspx.
It would appear that your cache and data folders would be the problem in their
current location as they would be private to each user on W7/2k8r2.
Dave
-Orig
Thanks Blair - I wish I was smart enough to find doc like that - direct hit!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/INSTALLDIR-and-Upgrades-reposted-in-correct-forum-tp5635805p5638820.html
Sent from the wix-users mailing list archive at Nab
Hi,
When I had a similar problem and I didn't have time to write a proper CA
I used SETACL.exe to set inheritable permissions on a registry key. Ugly
but fast.
http://setacl.sourceforge.net/
-Original Message-
From: dB. [mailto:dbl...@dblock.org]
Sent: 14 October 2010 21:54
To: General
1. MSI feature tree doesn't let you "grey out" the feature. However, you can
use a feature condition to totally remove it from the tree. If you do this
though you need to ensure that the feature is always enabled on remove or
else it will be orphaned. See Bob's post:
http://www.joyofsetup.com/200
Are you adding a ComponentRef for ASPcomponent0 under a feature? If not it
will not be included in the MSI.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Include-question-tp5631284p5638617.html
Sent from the wix-users mailing list archive at Nabbl
Try using the WiX Util extension element instead (it doesn't
remove all the permissions like the standard Windows Installer action does).
It's documented in the WiX help file.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Need-help-in-updating-pe
Thanks for this Blair,
Made it much easier to replace the standard dialog.
I am still having an issue though I'm afraid.
Basically I'm using a localised string to populate the scrollable text.
However the text doesn't appear when running the msi. Here is the
control snippet:
!(loc.Lice
Have you tried running ICE Validation of the MSI with and without the
patch(es) applied in something like Orca or InstEd ? That might give you
an idea as to what is wrong.
-Original Message-
From: pramodh_pe...@dell.com [mailto:pramodh_pe...@dell.com]
Sent: 14 October 2010 23:53
To: wix-u
26 matches
Mail list logo
