Hi Blair,
Thank you for your explanation. The following is my Upgrade table:
And the Custom Action is defined as:
I don't know how to use RemoveExistingProducts element.
I will try "NOT Installed AND NOT REMOVEOLD". Thank you again for your help!
Chunyan
-Ursprüngli
Hi Blair,
I have tried "NOT Installed AND NOT REMOVEOLD". But MyCA is always be called
for every upgrade. Is there something wrong with the Property='PREVIOUSFOUND'?
What can I do for Upgrade?
Regards
Chunyan
-Ursprüngliche Nachricht-
Von: Jiang, Chunyan (GE Healthcare)
Gesendet: Don
Hi,
> I have tried "NOT Installed AND NOT REMOVEOLD". But MyCA is always be called
> for every upgrade. Is there something wrong with the
> Property='PREVIOUSFOUND'? What can I do for Upgrade?
>
>
Try "NOT Installed AND NOT PREVIOUSFOUND".
>
>Minimum='1.0.0.0' IncludeMinimum=
Hi Kim,
It's cool! "NOT Installed AND NOT PREVIOUSFOUND" works! I changed the
condition to it, then upgrade. This time MyCA is not called. Now I understand
that the condition should match the property. Otherwise it won't work.
Cheers!
Chunyan
-Ursprüngliche Nachricht-
Von: Kim Gy
Hi Wix-user,
I want to define one Custom Action like this:
How can I get the computer name in wix and put it into the ExeCommand?
Regards,
Chunyan
--
Let Crystal Reports handle the reporting - Free Crystal Re
What about using the ComputerName property?
e.g.
or I use this for a deferred action, you could easily adapt this for your
needs with the [ComputerName] property:
Cheers
Richard
2009/8/6 Jiang, Chunyan (GE Healthcare)
> Hi Wix-user,
>
> I want to define one Custom Action like this:
>
There's a ComputerName property:
http://msdn.microsoft.com/en-us/library/aa368009(VS.85).aspx
So
2009/8/6 Jiang, Chunyan (GE Healthcare) :
> Hi Wix-user,
>
> I want to define one Custom Action like this:
>
>
>
> How can I get the computer name in wix and put it into the ExeCommand?
>
>
>
> Re
Hello Wix Team,
Can anyone please help me in resolving the errors found while
running Wix scripts using Wix v3.0.5419.0.
1. error LGHT0204 : ICE43: Co
mponent C_Rel has non-advertised shortcuts. It should use a registry key
under HKCU as its KeyPath, not a file.
2. error LGHT0204 : ICE57: Co
mpon
Hi Richard,
Thanks! [ComputerName] sounds good. It passed the compile.
Cheers,
Chunyan
-Ursprüngliche Nachricht-
Von: Richard Hollis [mailto:richhol...@gmail.com]
Gesendet: Donnerstag, 6. August 2009 15:45
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-use
Thanks John. I tried you suggestion. And it passed the compile. But how it
performs actually, I need to run the .msi.
Cheers,
Chunyan
-Ursprüngliche Nachricht-
Von: John Ludlow [mailto:john.ludlow...@gmail.com]
Gesendet: Donnerstag, 6. August 2009 15:39
An: General discussion for Wind
We are installing a web application and we are dependent on another project
that installs to the root web site only.
I would prefer to use a merge module from this company but they said we should
just copy the files we need from their installed directory.
So I'm looking for some advice.
Is the
Hi,
I' m working on a setup for our product. The setup has 2 features :
- First feature to install our service
- Second feature to install the web application in an existing web site
The two feature are optional : I want that users can install only the service
or only the web
Hi all, I am now using heat.exe to generate the .wxs file of one
directory with the command:
heat.exe dir "." -gg -nologo -sfrag -out test.wxs -template:product
, where the current directory contains thousands of files (because it's
the root dir of a web application).
Then I want to inclu
Hey Andrew,
I have confirmed that it is supported.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW
On Wed, Aug 5, 2009 at 3:37 AM, Andrew Dedman wrote:
> Anyone know if XP Embedded can handle an msi file? Does XP embedded ship
> with Windows
Set the SKIPCONFIGUREIIS property to 1.
-- Yan
-Original Message-
From: Loïc DELAMBRE [mailto:delam...@doxense.com]
Sent: Thursday, August 06, 2009 5:54 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Problem with IIS extension
Hi,
I' m working on a setup for our product. T
You can try transforming the resulting test.wxs with XSLT the way you
wish. See -t switch of heat.exe
-- Yan
-Original Message-
From: bonn deng [mailto:bonnd...@gmail.com]
Sent: Thursday, August 06, 2009 6:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to make use of
Hi Wix-users,
I have some Custom Actions, which should be called during Upgrade.
Actually I want them to be called in the beginning of Upgrade, before
remove files. So I set them as:
UPGRADINGPRODUCTCODE
UPGRADINGPRODUCTCODE
UPGRADINGPRODUCTCODE
But when I ran .msi, as the custom actions
According to the heat help, you should be able to add
-cg testComponents
to the heat command line to create a componentgroup in the generated wix
file. You can then add
to your feature to include the components.
-Original Message-
From: bonn deng [mailto:bonnd...@gmail.com]
Sent: 06
2009/8/6
> Send WiX-users mailing list submissions to
>wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>https://lists.sourceforge.net/lists/listinfo/wix-users
> or, via email, send a message with subject or body 'help' to
>wix-
I think you need to use a component group:
heat ... -cg WebSiteFiles
This wraps all your components up into a single component grouping that you
can then reference easily in your feature:
Richard
2009/8/6 bonn deng
> Hi all, I am now using heat.exe to generate the .wxs file of on
Bonn,
Are you trying to generate ComponentRefs for all the components in your
test.wxs file to use in your features?
Matthew Yost
Software Engineer
GLD Solutions, Inc.
-Original Message-
From: bonn deng [mailto:bonnd...@gmail.com]
Sent: Thursday, August 06, 2009 10:20 AM
To: wix-users@l
Yes, I am. Do you have any suggestion? Thank you!
>
>
> Message: 4
> Date: Thu, 6 Aug 2009 10:36:41 -0500
> From: "Matthew S. Yost"
> Subject: Re: [WiX-users] How to make use of the output .wxs file of
>heat.exe in WiX3.0?
> To: General discussion for Windows Installer XML toolset.
I wrote a tool for a web application that I was building an install for that
generated ComponentRefs based on a generated heat file. I uploaded the code to
Codeplex (http://wixgen.codeplex.com) so if you want to use it, just pull it
down and compile it. Hope it helps!
Matthew Yost
Software En
Thank you, it works now. I have found an old post about SKIPCONFIGUREIIS and
how to set it to 1 when a feature is unselected.
Regards,
Loïc
-Message d'origine-
De : Yan Sklyarenko [mailto:y...@sitecore.net]
Envoyé : jeudi 6 août 2009 17:25
À : General discussion for Windows Installer XM
Wow, thank you, I didn't mention such a param 'cause I'm reading the
help doc of wix.chm which doesn't say a word about this... Hope this could
help me out! ^_^
Message: 2
Date: Thu, 6 Aug 2009 16:31:51 +0100
From: "Peter Shirtcliffe"
Subject: Re: [WiX-users] How to make use of the output .wx
Found out some more info. It is an option when building an XP embedded
image. But it is not a default. So, you should definitely look to detect
what is on the system and you might need to install the distributable if it
isn't.
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.
Hey Bonn,
Just a friendly reminder. Features are only allowed to have 1600 components
according to MSI docs. Heat generates one component per file so I would
recommend breaking up your harvesting effort into more than one directory
and having more than one output file if you have greater than 1600
"NOT Installed AND NOT PREVIOUSFOUND"
The property identified in each UpgradeVersion element that does not have
OnlyDetect set to "yes" is used by the RemoveExistingProducts action to
perform the removal of the old version of the product.
For elements where OnlyDetect is set to "yes" the property
You still have a situation because if those files are updated after you copy
them, you still don't have the updated files.
If you know what the files are and where/how to find them (assuming they
would be installed before you), you could try the CopyFile element in WiX.
-Original Message-
Hey,
I have having a problem with the feature dialog when I re-run the installer I
get a random grey box
across the feature tree.
Below is a picture of it, I have removed all the text so don't worry about the
missing text
http://img11.yfrog.com/img11/2733/featuredialog.jpg
Does anyone know w
Is there a way to have Permission/PermissionEx (and I still haven't figured out
the difference) to retain the current ACL and only modify to add/remove what I
need to do on the folder specified?
What I'm trying to do is create a share on an existing folder but I have to
grant domain users read
Can you please provide source for context?
-Original Message-
From: Vinod Kulkarni [mailto:vinnukulka...@gmail.com]
Sent: Thursday, August 06, 2009 6:32 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix v3 script errors
Hello Wix Team,
Can anyone please help me in resolving
Thank you all, after using the param "-cg MyComponentGroup", now my
problem is solved! Thank you!
>
> --
>
> Message: 1
> Date: Thu, 6 Aug 2009 10:48:34 -0700
> From: Brian Rogers
> Subject: Re: [WiX-users] How to make use of
Thanks Brian, much appreciated
On Thu, Aug 6, 2009 at 23:56, Brian Rogers wrote:
> Found out some more info. It is an option when building an XP embedded
> image. But it is not a default. So, you should definitely look to detect
> what is on the system and you might need to install the distribut
PermissionEx doesn't remove the present ACLs, so this is the element you
need.
-- Yan
-Original Message-
From: Pierson Lee (PIE) [mailto:pierson@microsoft.com]
Sent: Friday, August 07, 2009 2:45 AM
To: General discussion for Windows Installer XML
toolset.(wix-users@lists.sourceforge.
Brian,
The issue of 1600+ components is just a warning, saying it might cause
problems for Win9x systems. If the installation will never target Win9x
and it is always a per-machine installation, is it safe to ignore this
warning?
Thank you.
-- Yan
-Original Message-
From: Brian Rogers
36 matches
Mail list logo