Thank you Steven, I like the logging option and am running with that for
now.
On Thu, Mar 14, 2013 at 3:00 PM, Steven Ogilvie wrote:
> Classification: Public
> Oops
>
> String tempString = session["MyProperty"];
>
> -Original Message-
> From: StevenOgilvie [mailto:sogil...@msn.com]
> Sen
On Thu, Mar 14, 2013 at 2:09 PM, chennam wrote:
> Is their any property setting possibility of Heat not be executed for
> every build?
>
I don't believe so. My first thought was to modify the Condition to execute
HeatDirectory only when the OutputFile does not Exists() but then it
occurred to me
Ok so for an update. After digging through the Burn source I saw it was reading
an XML file from the package (and I assume that it includes the GUID for the
original MSI and not the transform). That is when I noticed that there was
nothing that actually wrote the XML. So I was wondering if it wa
Hi,
I'm trying to use heat to harvest files.
I'd ideally like to in thi case anyway harvest all *.bat files from a directory
to go in to a component group.
Is this possible currently.
Help appreciated.
Cheers
Sean.
--
Ever
Classification: Public
Oops
String tempString = session["MyProperty"];
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: March-14-13 5:54 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using Property's values in Messages
You can do it various ways, t
You can do it various ways, the easiest way is to let QA see the value in the
MSI log file, in your product WXS file add:
after the install is done in your %temp% folder will be a MSI log file, look
for the property name and its value will be recorded...
or display the properties via custom actio
Hey all, can anyone tell me if there's a way to display the value of a
property? I'm doing registry searches for different product install
directories, and would like to display them to the QAs running the
installer.
--
Ev
Hi I was integrating wixproject into Main Project.
And below are the changes in Wix SETUP Project Properties.
This is generating the DropContent.WXS Fragment when ever project is build
(ie it is running Heat everytime the whole project is build.) But I want
Heat to be executed only once at first
Solved :)
Using this:
catch (Exception ex)
{
WriteErrorLogInstall(session, "Method failed: ", ex, true);
if (session != null)
{
session.Message(
InstallMessage.User + (int)MessageBoxIcon.Error
And that is what we are looking for, simplicity for the admins. Our Chained
product contains 5 main product installers and up to 59 language pack
installers and therefore we did not want to have the system admin to have to
enter so many installer .msi.
So having a single chain .msi to push woul
Ok, I am working with Jonathan today in my day job capacity and I have an
understanding of PROBABLY what is happening. If the WiX-devs list is better for
this, let me know...
Based on the install logs and the way BURN appears to work, transforms seem a
bit limited in how BURN handles them
I modified per your instruction, and then got a compiler error regarding
WixMbaPrereqPackageId and WixMbaPrereqLicenseUrl. So I followed the example
in
http://blogs.msdn.com/b/heaths/archive/2011/10/28/introducing-managed-bootstrapper-applications.aspx.
It again compiles, but when I run the
Not really sure what you are meaning by an embedded UI here. GPO publishes
MSIs silently to client machines.
Also its possible to push several MSIs as part of one policy (we have to
document this for our customers so they can install prerequisites) so I don't
see an absolute requirement for chaini
Thanks, that worked perfectly! I knew it was something simple I did months
ago, but just could not remember.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-in-the-ARP-tp7584342p7584352.html
Sent from the wix-users mailing list archive at Nab
If you're in DTF you might find that they have something that gets to
MsiProcessMessage(), a Session.Message or something.
Phil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Thursday, March 14, 2013 8:26 AM
To: General discussion for Windows Installer XM
I missed that feature when I downloaded the extended BA yesterday. I'll study
the Codeplex discussion and ask over there when I have more questions. I'll
also search wix-devs.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, March 13, 2013 11:00 AM
Try to not use 'ParentName="$(var.ProductName)"'. Just remove this code.
Alexey.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-in-the-ARP-tp7584342p7584348.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Classification: Public
I am using a C# dll and I can't seem to find info on how to use
MsiProcessMessage() in C#
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: March-14-13 10:26 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-user
1. Burn will not flood ARP with entries. By default, the MSI package
registration is suppressed so you'll only get the Bundle registration in
the end. Burn is used when you create a Bundle element using WiX v3.6+.
2. Merge Modules are mostly useful when sharing setup logic with people
that are not
I would probably apply an XSLT to transform the output of heat to something
more referenceable.
On Thu, Mar 14, 2013 at 3:27 AM, Stones wrote:
> Hi,
>
> I have an installer that is currently working by using heat to harvest a
> published website. This works perfectly and I get my site installe
You shouldn't use MessageBox. MsiProcessMessage() is the right way,
typically with INSTALLMESSAGE_USER.
Phil
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Wednesday, March 13, 2013 12:05 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Any ideas on ho
I've seen tangential posts regarding this, but no answer quite fit what I was
looking for.
I have a bootstrapper which will install several prereq's and then my product's
MSI. In testing, I noticed that if the product is uninstalled from ARP and
then the bootstrapper is run it thinks it is stil
Okay the 'product' term seems to be a bit overloaded here, even I have used it
in two different meanings.
So the one way we currently support is:
ComponentGroup 1 -> MSM 1 -> single feature MSI containing MSM 1 only
ComponentGroup 2 -> MSM 2 -> single feature MSI containing MSM 2 only
...
The oth
MSM is a Windows Installer standard, wixlib is not. Otherwise they are
similar in function with wixlib being lighter weight and more flexible.
But your scenario confuses me. An MSI can install one and only one
product. It would be more accurate to say the files for one feature goes
in M1 a
Hello,
I am trying to move from merge modules to wixlibs, but I am not sure whether
all the functionality is preserved.
Consider the following scenario:
- one product goes into the merge module M1
- other product goes into the merge module M2
- a MSI is created containing both M1 and M2 and insta
Hi,
I have an installer that is currently working by using heat to harvest a
published website. This works perfectly and I get my site installed.
The problem is now I need to add in some additional dll's because of
dependency injection. How do I find the created bin folder as part of the
instal
26 matches
Mail list logo
