Thank you for your reply. I know, that it can be that simple to use the
WixNetFxExtension. Unfortunately I need to also install on machines that have
no internet access and so I can't use it. That's why I copied some part from
the WixNetFxExtension and adjusted it to use the .Net exe I put on
On 13/02/2013 08:01, Ogrodowski, Sabine (ehem. Frauenhoffer) wrote:
Thank you for your reply. I know, that it can be that simple to use the
WixNetFxExtension. Unfortunately I need to also install on machines that have
no internet access and so I can't use it. That's why I copied some part
I found this bug on this topic, but it is marked as closed, so I thought it
should work...
http://sourceforge.net/p/wix/bugs/2635/
-Ursprüngliche Nachricht-
Von: Bruce Cran [mailto:br...@cran.org.uk]
Gesendet: Mittwoch, 13. Februar 2013 10:15
An: General discussion for Windows
Your last approach is correct. In general, you:
Place resources in a fragment in a separate file.
Add the file to the project.
Reference resources from your main wxs file (or any wxs file that it already
references) using an xxxRef.
When candle runs, it compiles the wxs file into a wixobj because
That, or add the generated wxs file to your project in visual studio.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 13 February 2013 07:14
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe
SET WIX=toolset-directory
SET
Hi,
Some times uninstallation works, but second setup installation does not
started without uninstall first setup or restart.
Could you provide any solution for this?
Thanks,
Kannan
--
View this message in context:
Hi,
I'm having issues trying to get a patch built with WiX (using the Patch
Creation Properties method) to apply to an MSI (also built with WiX) that has
been multi instance transformed. I've logged my efforts to get it working on
StackOverflow:
Thanks for this good explanations!
Regarding this:
You should probably set the Burn bundle as related to the MSI so when a
user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the
user's system will have the (invisible) Burn bundle still registered which
could cause problems if
Burn only fails back to the MBA prerequisite BA if it can't create the
AppDomain it needs. Look at BootstrapperApplicationCreate in
src\ext\BalExtension\mba\host\host.cpp.
Introducing additional dependencies for a BA seems wrong to me. If you are
using this custom dependency to modify machine
Hi,
Does anybody have an example on how to install an Isolated Shell (of Visual
Studio) using WiX?
http://msdn.microsoft.com/en-us/library/vstudio/bb685691(v=vs.100).aspx
There are some examples I can find on the web, but they're pretty much all
out-dated.
Met vriendelijke groet / kind
I am trying to combine InstallScopeDlg and InstallDirDlg into a single UI and
have been trying to get it to set INSTALLFOLDER then call the InstallDirDlg
which causes an error.
I am changing the property with the following.
Publish Dialog=InstallScopeDlg Control=Next Property=INSTALLFOLDER
Thanks for your feedback.
We are using Wix3.5 (currently looking at moving to 3.7). Unfortunately, using
BinaryRef caused an error with candle. However, we tried adding a empty
Component to the fragment file and then referenced the dummy component from
within the master.wxs file, which forced
But even though setting:
Bundle ... DisableModify=yes DisableRemove=yes
MsiPackage ... *DisplayInternalUI=yes Visible=yes*/
I stil get the Bootstrapper UI visible first. Then When I click
Install I got the MSI UI visible in front of Bootstrapper UI. And when
MSI UI are finnish the Bootstrapper
Probably because WiXUI doesn't have any idea what your INSTALLFOLDER property
is or does.
If you're trying to set the contents of the PathEdit in InstallDirDlg you
should probably use the WIXUI_INSTALLDIR property associated with it as
detailed in the manual -
You have to write your own Bootstrapper Application to replace the use of
WiXBalExtension in that case -
http://wix.sourceforge.net/manual-wix3/bootstrapper_application.htm
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
Okay, I see we have to go that path!
Sorry to repeat, but this question also:
You should probably set the Burn bundle as related to the MSI so when a
user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the
user's system will have the (invisible) Burn bundle still registered
Hi all,
I ran into the strangest problem on a customer's machine today. He was
installing a new version (MAJOR upgrade) of our software which has the
authoring below. We set INSTALLDIR from UPGRADEDIR if a previous
version is installed (SetUpgradeInstallDir custom action) and make the
Hi
During the install of our product we need to know how many cores the CPU has.
Does Wix have this capability?.
Thanks
-
Stephen Turner
AudioScience, Inc.
--
Free Next-Gen Firewall Hardware Offer
Solved!
It seems that (an older version) of Canon Easy Web-Print EX which
shipped with the (in our case) Pixma MG8120 was putting its Uninstall
values directly beneath the Uninstall key instead of in its own
product-specific key and didn't clear them on uninstall.
So for a new install of our
That error is just enforcing an ICE rule that says you cannot use the same
property name in multiple upgrade table entries. You need a unique property
name for each of the upgrade rows.
Phil W
-Original Message-
From: Vern Graner [mailto:v...@txis.com]
Sent: Tuesday, February 12, 2013
No, it doesn't. But I've already answered that on Stack Overflow for you.
From: Stephen Turner sgtur...@audioscience.com
Sent: Wednesday, February 13, 2013 12:29 PM
To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
Subject: [WiX-users]
I am learning to use wix and have come across an issue that doesn't seem to
make sense to me.
I have created 2 CustomActions one in c++ and one in c#. (Purely for
experimental purposes)
Both CAs simply contain a MessageBox. (To prove they are being called). And
both are called correctly.
For C# using DTF it's MMsiBreak. For C/C++ it's MsiBreak. Also you have
to restart the machine after setting the env var for the service control
manager to pick up the environment change and pass it along to the Windows
Installer service.
I've debugged many DTF custom actions it's entirely
Hi
I know EnableProjectHarvest was set to false by default in 3.6 due to
harvesting complications. To enable it you had to go and set it to true.
But this doesn't appear to work for 3.7.
What is the state of harvesting in 3.7?
For me it works fine in 3.5, (and in 3.6), and I would like to
My MSI has two dummy feature as listed below.
Feature Id=FULLPRODUCTION Title=RMSSetupInstaller
ComponentGroupRef Id=ProductComponents /
/Feature
Feature Id=ADMINCONFIGURATIONTOOL Title=RMSAdminInstaller
ComponentGroupRef Id=AdminComponents /
Hi Aaron,
Did you find the solution ... I was looking for solution for website
Harvesting.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-Website-Harvester-Status-tp3177602p7583566.html
Sent from the wix-users mailing list archive at
Hello Guys,
We have a very intermittent bug in the installer that we are developing.
We have a bootstrapper that uses WiX 3.5 and has the following code:
/var transactionSession = new Transaction(ANTON,
TransactionAttributes.None);
foreach (var msiPackage in msiPackageList)
{
I think I found the issue.
In bundle msipackage definition I need to define the following. Property to
make it work
msiproperty name=ADDLOCAL value=[ADDLOCAL]/
Sent from my Windows Phone
From: Nan Zangmailto:naz...@microsoft.com
Sent: 2/13/2013 7:15 PM
To:
28 matches
Mail list logo
