Hi All,
I've just reinstalled a new laptop with VS2008, Wix3.5 but now when I try
build my projects the setup projects fail to build with the following error:
heat.exe(0,0): error HEAT5307: Build failed.
All the links I see on the internet refer to C++ projects. These however
are C# projects.
Unless I'm totally off base, the line provided does persist
ARPINSTALLLOCATION in the unistall environment (it's being explicitly set
after CostFinalize regardless of whether this is an initial installation,
repair, an update, or a removal.) Am I mistaken?
As for CUSTOMDIR, I didn't provide thos
PS: The reason WiX toolset doesn't set ARPSYSTEMCOMPONENT yet is because I
wanted to leave everyone an easy escape hatch in the case that Burn got
confused and failed to uninstall or upgrade a version of WiX v3.6. When I
trust Burn enough (which is pretty soon actually), we'll set
ARPSYSTEMCOMPONEN
On 29-Aug-11 11:15, Sheehan, Andrew wrote:
> Does v3.6 support the indication/usage of a custom EULA/License file?
Yes. See "Specifying the WiX Standard Bootstrapper Application License"
in wix.chm.
--
sig://boB
http://joyofsetup.com/
--
On 29-Aug-11 18:47, Shaun Hayward wrote:
> My impression that ARPSYSTEMCOMPONENT told the MSIEXEC not to write any ARP
> registry entries came from an MSDN blog from some 6 years ago:
>
> http://blogs.msdn.com/b/heaths/archive/2005/08/05/448198.aspx
>
> So the information may not be correct.
It's
Thanks, Phil.
My impression that ARPSYSTEMCOMPONENT told the MSIEXEC not to write any ARP
registry entries came from an MSDN blog from some 6 years ago:
http://blogs.msdn.com/b/heaths/archive/2005/08/05/448198.aspx
So the information may not be correct.
Ultimately I'm looking to see if use of
ARPSYSTEMCOMPONENT is just a property you set in the property table of the MSI,
like any other property. There's no need for anything special to set it.
" As I understand this property of MSI files, it will prevent the installation
from writing any registry entries for the MSI in Add/Remove Pro
ARPINSTALLLOCATION is a property that people set to make their install location
visible via supported MSI APIs. It doesn't get persisted into the uninstall
environment unless you persist it, and the same is true of CUSTOMDIR. What are
you trying to accomplish here?
Phil Wilson
-Origina
have tried with and without CDATA tags, but can't get the behavior I want
regardless of what I do!
http://schemas.microsoft.com/wix/2006/wi";>
...
...
Installed AND NOT
UPGRADINGPRODUCTCODE AND
(ARPINSTALLLOCATION >< $(var.ProductName))
...
The installation works beautif
With thanks to Tobias and Cody, I'm making progress on WiX Burn with a managed
WPF UI.
I've used WiX to create an MSI and Burn to create a bootstrapper for it. After
installing with the bootstrapper, I have two entries in Add/Remove programs:
one for the MSI, one for the bootstrapper.
There ha
Hi,
I want the user to allow to reselect features on the repair mode. He should
be able to select other features (this is no problem since no other files
will be installed, but the custom actions are different depending on the
selected features).
This works already by using Custom UI and the feat
> · What changes should I make in TFSBuild.proj files?
The WiX solution is integrated like other solution into TFSBuild.
Add the the needed SolutionToBuild + configurationToBuild. E.g that
should be something like following:
Release
x86
> · What change
In general, you can't assume the UI is going to run for a repair. For example,
running "Repair" from the Control Panel button runs the repair in "Basic" mode
with only the basic progress dialog showing. It works from the
MaintenanceTypeDlg when you press the "Change" button off Control Panel b
Hello All,
Does v3.6 support the indication/usage of a custom EULA/License file?
http://schemas.microsoft.com/wix/2006/wi";>
removed for brevity
--
EMC VNX: the world's si
Hi,
I am working on a Wix3.0 installer, This installer is having one driver of 54MB
to be copied in the user's temp folder before installation, and delete the same
after installation from the temp folder.
When I am doing repair from the control panel , i am observing that the size
gets dou
You can do this yourself by using the upgrade table and to check for the
product version you are looking for and only set the property. You can then
use this property to set an installation condition to display a message that
the pervious product must be manually removed before continuing.
Ple
Hi,
I am wondering if there is any way to have Wix check if the
product is already installed (irrespective of the version), if so ask
the user to uninstall it manually (or ask the user if he wants it to be
uninstalled by Wix if possible).
Then Wix would just do a full
installation as i
17 matches
Mail list logo