Hi,
As part of your install you'll have to save the property values to the
registry. See this for more info:
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern
John
Wintellect
http://www.wintellect.com
+1-877-968-5528
-Original Message-
From: Thai
Mr Sandher gave me some useful tips for building a platform neutral
setup and I'm trying to follow his advice as best I can.
http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx gives
an example of one project that outputs both x86 and x64 MSI files.
But I've tried different build set
Hello... please help me with this issue.
The installer sets a default value and allows the user to enter a new value.
When the user enters a new value, it is used during the installation. But the
default value is used instead of the user-entry’s new value during
uninstallation. I found thi
Hello... please help me with this issue.
The installer sets a default value and allows the user to enter a new value.
When the user enters a new value, it is used during the installation. But the
default value is used instead of the user-entry’s new value during
uninstallation. I found
I think you are correct, MsiPublishAssemblies is scheduled after
ConfigureComPlusInstall (I am not sure how it works for a standalone
.Net COM+ component). You could try moving the ConfigureComPlusInstall
after MsiPublishAssemblies but it sounds like you have a solution now
although I didn't think
Hi Ed,
This is probably due to what I was asking about earlier in this thread:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg43495.html
And I have not got around to submitting a bug request yet.
Thanks,
Murray
Date: Fri, 28 Jan 2011 05:28:04 -0800
From: Rob Mensching
Subject: R
6 matches
Mail list logo
