I have now modified my build script to use a locally build msi installer and
comparing it with a version build on my build server yesterday.
There is no practical difference between the two msi files except the version
numbers.
Is that why I keep getting errors?
I get the following error
Can you pass the credential info to the CA and do the impersonation inside
the utility?
Or install the utility and call it on first run?
-Original Message-
From: Joe Barker [mailto:joeb...@gmail.com]
Sent: 02 May 2013 16:36
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom
I'm already passing the credential info into the CA. Do you mean passing it to
the CA, to the pass to the utility and run impersonation in there?
I'll have to look and see if there's a way we can guarantee that the utility
will be called on first run, as our application is a web-based
Hello.
I create an msi für x64.
A Component i must mark with Win64=yes.
But a Config file has no platform.
What is the right way to handle this?
Product Id=* Name=MyApp Language=1031 Version=2.0.3
Manufacturer=My Company UpgradeCode={guid}
Package InstallerVersion=200 Compressed=yes
Hi,
I was looking for a way to add files from multiple directories with
HeatDirectory element.
Also, I would like to know if there is a way to append the fragment generated
by HeatDirectory to an existing .wxs file.
Regards,
Victor Mukherjee
I never use wild cards...some day you will distribute unwanted files to
customers.
How often is your setup changes?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Alternative-to-Heat-exe-tp7585574p7585598.html
Sent from the wix-users
Bug ID for this issue is 3287, the only solution I found so far is to build the
MSI in a VM that doesn't have FIPS (SHA2) enabled.
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: May-02-13 7:36 PM
To: General discussion for Windows Installer XML
My problem is different. It's my installer exe that can't run on users with
windows 7 professional. I can build the installer fine.
-Original Message-
From: Jonathan Racine [mailto:jonathan.rac...@hybris.com]
Sent: May-03-13 10:11 AM
To: General discussion for Windows Installer XML
I was guessing at what exactly you are doing. Yes get the utility to do its
own impersonation.
Or run a post install configuration utility.
-Original Message-
From: Joe Barker [mailto:joeb...@gmail.com]
Sent: 03 May 2013 10:11
To: General discussion for Windows Installer XML toolset.
Hi tom,
So their is a way to you use Wild card? As we have package without unwanted
files. And in WIX project we want use a wild card to get all the files under
package folder into MSI .Instead of specify each file as component to pull
into MSI.
We have integrated the MSi to dailybuild .So
In visual studio under build you need to define a preprocessor variable
that points to the location of the root directory. Example:
DatabaseDir=..\Folder.
Then under build events you need to write a Pre-build Event command line to
have heat generate the wxs file every time you make a build.
Hi,
I want to change the content of the config file based on the machine
(SPECHW01,SPECHW02..) the MSI gets deployed.Below is the content of the
file and node Param I want to change.
scheduling
agent
http://web.service/keepalive.aspx
LogActivitytrue/LogActivity
In general, it would be better to use the HeatDirectory / element. For
example:
EnableProjectHarvestingTrue/EnableProjectHarvesting
Target Name=BeforeBuild
HeatDirectory ToolPath=$(WIX)bin\
Directory=..\Folder
Jeremiah, yes, the relative pathing is correct. The problem is not about
finding the file but rather the rollback logic. Thank you for the suggestion
though.
Greg
--
Message: 1
Date: Thu, 2 May 2013 18:20:10 -0500
From:
Bingo! Thank you Bob. I really didn't need those since I wasn't changing the
default flow anyway.
Greg
Date: Thu, 02 May 2013 21:35:54 -0400
From: Bob Arnson b...@joyofsetup.com
Subject: Re: [WiX-users] Why is RollbackBoundary discarded?
To: wix-users@lists.sourceforge.net
Message-ID:
In general, with the WiX toolset it's generally best to only add the
attributes you need.
On Fri, May 3, 2013 at 9:47 AM, Prosch, Greg gregpro...@a-tsolutions.comwrote:
Bingo! Thank you Bob. I really didn't need those since I wasn't changing
the default flow anyway.
Greg
Date: Thu, 02
You could harvest them all and use an XSLT to filter them. The command line
heat accepts a -t parameter to transform the output, and the MSBuild task
should have a related property.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: Friday, May 03, 2013 9:57
Hmm,
I think I would have one config file and conditionally modify it with CA's
like XmlFile/XmlConfig. I'd also try to eliminate the machine name dependency
and instead use a dev/test/live burn bundle passing a parameter via a
MsiProperty to the installer.
-Original Message-
From:
Hello,
Does anybody have experience installing drivers with Wix?
I have a NIC GigE filter driver that installs fine but does not add the
service to the NIC's on the computer. How do I install the network
service in wix?
Does anybody have experience installing Network service drivers?
I haven't done it myself but I know others have used the Difx extension to
do so.
On Fri, May 3, 2013 at 10:33 AM, Michael Ogilvie
michael.ogil...@pixelink.com wrote:
Hello,
Does anybody have experience installing drivers with Wix?
I have a NIC GigE filter driver that installs fine
I use Wix to install drivers but only USB/HID drivers which are straight
forward.
The difx:Driver element goes with the component with File element of the
inf file. Other driver components do not need the difx element.
You need this:
I have used HeatDirectory to harvest a folder with many subdirectories and
files, but Heat.exe report an error because the filepath of an item is larger
than 260 chars (with the name and the full subdirectories path)Is there any way
to harvest a folder with may subdirectories as the single
That character limit on paths is imposed by .NET. :-(
On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci mark...@live.it wrote:
I have used HeatDirectory to harvest a folder with many subdirectories and
files, but Heat.exe report an error because the filepath of an item is
larger than 260 chars
Unfortunately, the .NET Framework doesn't handle that.
On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci mark...@live.it wrote:
I have used HeatDirectory to harvest a folder with many subdirectories and
files, but Heat.exe report an error because the filepath of an item is
larger than 260
Have not at all tried this, and it may not work or cause all other kinds of
issues... But judging from
http://msdn.microsoft.com/en-us/library/aa365247(v=VS.85).aspx , you could try
prefixing the fully qualified path with \\?\
The Windows API has many functions that also have Unicode versions
It's not just .NET. Many functions in the Win32 API have the same limitation
unless you use UNC path names (in which case the limit is 32767 characters).
Daniel Madill
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: May-03-13 2:10 PM
To: General discussion for
On 2013-05-03 20:10, Edwin Castro wrote:
That character limit on paths is imposed by .NET. :-(
I use https://alphafs.codeplex.com/ to work with
pathes up to 32000 characters. I hope they will fix it
in .NET sometime.
Marc
The way it works in MSI isn't really mysterious. Basically the property name
needs to be public (and that means it must be all uppercase). If WiX does
its thing properly then you can open the generated MSI file with an editor
such as Orca, look in the Properties table, and in the Property table
I was not using managed code custom actions...
I was doing:
Property Id=WEBAPPPOOL_PASSWORD Hidden=yes Secure=yes/
CustomAction Id=CA_WebAppPoolPassword.SetProperty
Property=CA_WebAppPoolPassword.
Value=WEBAPPPOOL_PASSWORD=[WEBAPPPOOL_PASSWORD]/
Tried adding: HideTarget=yes that didn't help
The Issue I am working on is for Production environment where content of
Web.config is different for 5 machines at below node.
scheduling
agent
http://web.service/keepalive.aspx
LogActivitytrue/LogActivity
/agent
/scheduling
For other environments we have only
The better option is to have one Web.config file and 6 other components
(containing the XmlFile elements) with conditions on them for writing the
appropriate values.
Not that I like the idea, but you could have 6 Components with a Web.config in
each and a Condition element for each component
Unfortunately, won't work in NETFX and MSI APIs don't like the Unicode path
format either.
On Fri, May 3, 2013 at 11:15 AM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
Have not at all tried this, and it may not work or cause all other kinds
of issues... But judging from
Steven,
Tried adding: HideTarget=yes that didn't help Indeed!
I'm even tried to remove logging from the custom action and I still see the
password...
I've even checked MsiHiddenProperties and see that PASSWORD is listed along
with CA_DBAction... Not in SecureCustomProperties... I added
Replying to JeremiahF with the original problem - I replied to you to
preserve most of the thread.
Phil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Friday, May 03, 2013 11:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Running Wix 3.6, I had to follow one of many examples on the net on adding
PackageGroup to my code to check/install .NET 4.0, just to get my Setup to
build.
Here's the thing...I know Setup requires .NET to run, but I DONT want to check
for .NET, and I don't want to package the .NET installer.
I'm repeating myself to attempt to make this clear. This appears to be the
part of the log that you are worried about:
=
SFXCA: Extracting custom action to temporary directory:
C:\WINDOWS\Installer\MSI1045.tmp-\
SFXCA: Binding to CLR version
Hello,One of our clients is encountering a setup failure with the following
msg: '0X80070002 - The system cannot find the file specified.'The log file is
below. The install scope is perMachine. Any ideas on why it would be failing
when trying to cache the bundle? This is the first time we've
I'm using Burn v3.7.1224.0. What is the meaning of the following cmdline
present in the install log:
cmdline: '-burn.unelevated BurnPipe.{BA274BA7-1C44-402F-9E0C-5919915C3ADC}
{1B81FC8C-86AE-416C-AD37-DC7B377EDBCB} 716'
In other words, under what circumstances would a user execute the
Aha I stand corrected :) have a good weekend all
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: May-03-13 7:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] WiX-users] Hide/blank out Passwords in MSI log file
Replying
Your right Phil, it is a custom action that is creating the connection string,
as per the log below, luckily our connection string is encrypted...
For me, I took out the custom action to set the property and that solved my
issue... (I am using a Publish element in the dialog the sets the
Do you have the correct version of .net installed?
On May 3, 2013, at 7:43 PM, - Arzola - alphaq...@hotmail.com wrote:
Hello,One of our clients is encountering a setup failure with the following
msg: '0X80070002 - The system cannot find the file specified.'The log file
is below. The
41 matches
Mail list logo
