So I figured out that I needed the license payloads to look like this:
Payload Id=some_id Name=1031\license.rtf SourceFile=path_to_license.rtf
/
With the important bit being that the name is LCID\license.rtf. The only way I
was able to figure this out was by looking at through the wix
No, I did not. Must be a relatively new thing (I haven't worked on my BA for a
while due to previous bugs in WiX), I didn't have to do that last time. Thanks
for explaining. :-)
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 9. February 2012 04:54
To:
My RemoveExistingProducts looks like this:
RemoveExistingProducts After=InstallInitialize /
What exactly does towards the end mean? InstallFinalize?
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: 8. February 2012 19:06
To: General discussion for Windows
I'm making an installer which must configure a web service it installs. It
dynamically generates properties which hold the data collected from the
user in the UI sequence, installs the service and sets the parameters.
SetParams CA uses dynamic properties generated in the UI sequence. To
access
?if is a pre-processor directive and is acted upon during compilation not
at install time.
You can detect the software and set a property, this property can be used in
a condition on a component or a custom action.
-Original Message-
From: Hari kris [mailto:harikr...@hotmail.com]
Sent:
*Problem:*
I have a User Requirement in which a file would not be installed if a
Prerequisite application is absent on users machine. But after installing my
product, when user would install that Prerequisite application, he would run
my installer and choose repair to install that missing file and
On Thu, 09 Feb 2012 07:57:52 +, Ian Williams wrote:
So I figured out that I needed the license payloads to look like this:
Payload Id=some_id Name=1031\license.rtf
SourceFile=path_to_license.rtf /
With the important bit being that the name is LCID\license.rtf. The
only way I was
Hi,
I have the following problem installing to a path read from the registry.
I'm using WIX 3.5 (and currently testing on a Win7 64-bit).
I'm doing a registry search like this:
Property Id=APPINSTALLDIR
RegistrySearch Id='TheAppPath' Type='raw'
Root='HKCU'
No you need to know the name of the standard or custom action that you want
it to run after or before.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-not-running-tp7263897p7269311.html
Sent from the wix-users mailing list archive at
If you are using a condition on your component then you set
Component/@Transitive to yes. That should force Windows Installer to
reevaluate the condition during reinstall.
--
View this message in context:
Windows Installer does this be design so you really shouldn't try working
around it. But, see this post for more information:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-allow-32-bit-installer-to-write-to-C-Program-Files-td5544693.html#a5550286
light 3.6.2520.0 fails when run on the following file.
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle
ProgramFilesFolder = Program Files (x86) -
http://msdn.microsoft.com/en-us/library/aa370881.aspx
ProgramFiles64Folder = Program Files -
http://msdn.microsoft.com/en-us/library/aa370880.aspx
You can't write to 64-bit locations from 32-bit processes such as msiexec
running your x86 package.
Hi jhennessey
Thanks for the reply.
Yes, there is a condition on the component which is defined by a vbscript
custom action scheduled in Execute Sequence after CostFinalize, so that is
running during reinstall.
*But what if the component is not installed at first installation? Would
But what if the component is not installed at first installation? Would
Component/@Transitive=yes make it to install during reinstall?
Yes, as long as the component condition evaluates to true during reinstall.
Take a look at the WiX help file. It describes the attribute very well.
--
View this
Thanks a bunch
I will definitely give it a try.
Best regards
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Installing-a-Component-while-Repair-Or-Reinstall-tp7269151p7270180.html
Sent from the wix-users mailing list archive at Nabble.com.
Thanks for the help Sam.
Yes, I read your other thread (which was VERY helpful, by the way). So far
your comments are the same as mine. Over the next week or two I'll find out if
there are any more issues that you haven't commented on, and I'll be sure to
follow up in the thread.
Thanks
And another one is here
http://www.it-seminare.de/serversysteme-infrastruktur/ms-backoffice/windows-installer-xml-wix.html
http://www.it-seminare.de . I did one for them this week.
--
View this message in context:
Here is the situation: I have this application that is available both as
32-bit and 64-bit. Now I'm building an installer for an SDK for the app,
consisting on documents, .NET samples and other files. These are all
platform independent. However, they (some of them at least) must be
installed in
On 09-Feb-12 12:22, Sam Morris wrote:
doesn't replace any colons already in the Prefix attribute, so later on
the Binder gets confused when it splits the string on colon
characters...
Yep, not good.
I can file this as a bug if someone can add me to the project (sf
Anyone can file bugs.
--
Echo on the question.
I have exactly the same problem:
In my product V1.0, I have
FeatureCommon (always be installed)
Common.dll
FeatureA (optional)
A1.dll
FeatureB (optional)
B1.dll
In my product V1.1 I added A2.dll to feature A
21 matches
Mail list logo
