Hello,
I am trying to change a browsers default search engine using a Wix
installer. I see this done in a lot of installers but i can't seem to find
how to do it in Wix. I'd appreciate any advice :-)
Thanks
David Baker
Apart from the former being easier to add in project properties, what would be
the pros and cons of using project Pre-build Events compared to Target
Name=BeforeBuild Exec Command=...?
--
Everyone hates slow websites.
Hello,
My program has a .NET 3.5 prerequisite and I have used Burn and the
standard code successfully on Windows Server 2008 SP2.
On Windows Server 2012 however, .NET 3.5 and many other prerequisites need
to be installed via the Server Manager as features instead and cannot be
installed via an MSI
Hi I am trying to delete a hidden segment when installing a web application.
I am using the following code:
CustomAction Id=DeleteHiddenSegment Return=asyncNoWait
Directory=TARGETDIR
ExeCommand=[SystemFolder]inetsrv\appcmd set config
/section:requestfiltering
Keep deleting parts of the execommand string until it compiles. The quot; s
are most likely causes.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 30 January 2013 12:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] IIS- delete hidden segment
Peter,
Thanks it seems to be the square brackets it's not liking. Not sure if the
command will do as expected but I will test it.
Kind Regards,
Natalie Carr
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, January 30, 2013 12:34 PM
To: General
Oh, of course. It tries to interpret anything in square brackets as a
property name and [segment=quot;binquot;] isn't a property name. If you
need literal brackets in the string then you have to escape them as [\[] and
[\]]
See http://msdn.microsoft.com/en-US/library/aa368609.aspx 5th bullet.
I installed WIX using wix37.exe and I opened the command prompt and typed
candle.exe. But I got the following message, 'candle.exe' is not recognized
as an internal or external command,
operable program or batch file. I searched for candle.exe in My Computer and
I didn't get any result. I am
WiX is not in the path, use %wix%bin\candle
Neil
I installed WIX using wix37.exe and I opened the command prompt and typed
candle.exe. But I got the following message, 'candle.exe' is not
recognized as an internal or external command,
operable program or batch file. I searched for candle.exe
If you type echo %wix% (without the quotes) you will get the path of the
wix installation. Candle.exe is in the bin subdirectory of that location
-Original Message-
From: Kesavan, Lakshminarayanan IN BLR STS
[mailto:lakshminarayanan.kesa...@siemens.com]
Sent: 30 January 2013 13:06
To:
WIX gets installed to: C:\Program Files (x86)\WiX Toolset v3.7\bin
That folder is not in your PATH environment path, you will need to add it or do
at the command prompt set PATH=%PATH%;C:\Program Files (x86)\WiX Toolset
v3.7\bin;
Steve
-Original Message-
From: Kesavan,
When I run the candle.exe, I am not getting .wixobj file. Where this file
will get gerenated. Below is what I am doing.
C:\ candle.exe C:\Documents and
Settings\123\Desktop\SampleFirst\SampleFirst.wxs
Windows Installer Xml Compiler version 3.7.1224.0
Copyright (C) Outercurve Foundation. All
Do basically there is no way to simulate the old bootstrapper from the old
vdproj setup projects? It would be nice if we could configure for this
behavior. I would expect many other shops would want the same behavior . . .
Maybe something like an attribute on MSIPackage that is equivalent to
No it was not in the references, I normally have to search external to the
WiX doc to find answers. Think it was an answer in stackoverflow which I
know needs to be taken with a grain of salt ;)
Thanks,
John J. Hughes II
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
The wixobj should be in the current directory unless you specify the -o or
-out switch
If you type candle /? It will describe the options.
-Original Message-
From: Kesavan, Lakshminarayanan IN BLR STS
[mailto:lakshminarayanan.kesa...@siemens.com]
Sent: 30 January 2013 13:36
To:
Super, thank you
Kind Regards,
Natalie Carr
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, January 30, 2013 12:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] IIS- delete hidden segment error
Oh, of
If you do a web search on where is the default search engine registry
there are a bunch of articles about where it's stored. Because it's a
registry key, the WiX work is just setting the required keys to whatever
values you want.
Phil
-Original Message-
From: David Baker
Hi Neil,
You said: I also forced a version number for each file to ensure that if I
had to perform an upgrade the file would be overwritten REGARDLESS if it had
changed forcing integrity of the application. How did you do this?
Wes
-Original Message-
From: Neil Hayes
One way would be to designate one file as the KeyPath file, and make the other
files CompanionFile's of the KeyPath file. Effectively, the version of the
KeyPath file becomes the version of all of its CompanionFile's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry
Hi guys,
I'm having a question about Permission usage. Referring to
http://wix.sourceforge.net/manual-wix2/wix_xsd_permission.htm, I have the
following codes, I use a domain account(with administrator privilege) to
install it, but I couldn't access the install dir due to no permission. What's
Hi,
Can anyone tell me the correct way to add a Script Map to a web application
via wix? I have this but it's not adding the dll. It is also an ASPAI
module.
Component Id='WebVirtualDirComponent'
Guid='52D0B071-0801-4B93-8C8F-F5FC92DD8D8F' Directory='INSTALLLOCATION'
There is a bug open on this. The bug has been open since the beginning because
it's not an easy problem to solve. smile/
-Original Message-
From: Simon Detheridge [mailto:si...@widgit.com]
Sent: Tuesday, January 29, 2013 3:25 AM
To: General discussion for Windows Installer XML toolset.
I'd argue your best bet is to use the RestartResource element in the Util
extension to add the resource to the restart manager and let it do all the work
for you. In the case of Office apps, it should be particularly better because
Office apps register with restart manager and automatically
From the wix manual: GenericRead YesNoType specifying this will fail
to grant read access
Im not sure if GenericAll overrides that or not.
Try adding:
Read=yes ReadAttributes=yes ReadExtendedAttributes=yes
ReadPermission=yes
-Original Message-
From: Kun Shi (ofox)
I had problems with that it would work on install but not uninstall or vice
versa, I gave up and used the custom action...
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: January-30-13 10:12 AM
To: General discussion for Windows Installer XML toolset.
What do you mean by to put some of the components into a separate dll ?
-Original Message-
From: Harmon, Joseph [mailto:jhar...@illumina.com]
Sent: Monday, January 28, 2013 12:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle Installer size
If the task at hand is simply to update a config file before building a MSI,
this could all be done with MSBuild and could be outside the scope of the
wonderful world of Wix. Also, if this value could change per install or per
customer, then it would be easier to store the base config in the
Really need some help with this!
thanks,
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Weird-Repair-happening-tp7583229p7583272.html
Sent from the wix-users mailing list archive at Nabble.com.
What does the log file say?
On Wed, Jan 30, 2013 at 8:51 AM, StevenOgilvie sogil...@msn.com wrote:
Really need some help with this!
thanks,
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Weird-Repair-happening-tp7583229p7583272.html
Here is original listing and I have attached the log
I have installed my product and it works like a charm...
I have modified my install to work with Repair since I have a lot of custom
actions and 5 merge modules.
When I run repair all is good EXCEPT all files are being installed in 1 folder
I have a Wix 3.6 Burn project. The bundle has a condition that should
require Windows Installer 4.5 to be installed.
Bundle Name=Project
Version=0.1
Manufacturer=MyCompany
UpgradeCode=MyGuid
Condition=VersionMsi = 405
I have seen it on Windows 7 and on Windows XP with Windows Installer 4.5
installed.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
I believe what you want is a bal:Condition Message=Your message goes here
VersionMsi = 405/bal:Condition instead of a bundle condition.
-Original Message-
From: Eric Potter [mailto:eric.b.pot...@gmail.com]
Sent: Wednesday, January 30, 2013 2:05 PM
To: wix-users@lists.sourceforge.net
I used the bal:Condition and it worked. Thank you. But I had to chance the
version number from 405 to v4.5.
bal:Condition Message=Your message goes here VersionMsi =
v4.5/bal:Condition
In the future, how do I know which version number syntax to use in various
places?
Has anyone experiences LGHT0103 after upgrading from 3.5?
When performing builds in 3.5 light would respect a relative path of the
current directory, ie. Directory Id=TARGETDIR Name=SourceDir
FileSource=SourceDir\VC\.
Since the upgrade I've had to add $(sys.CURRENTDIR)\ to each FileSource or
From Wix documentation page,
http://wix.sourceforge.net/manual-wix3/daily_builds.htm, it says to modify
.wixproj file and add following lines:
WixToolPath$(SourceCodeControlRoot)\wix\3.6.3220.0\/WixToolPath
WixTargetsPath$(WixToolPath)Wix.targets/WixTargetsPath
The burn engine drops everything into one large executable, i.e. Setup.exe.
I'm just looking for any way to make the executable smaller so its startup
performance will be improved, by perhaps doing something similar to using
reflection to reference a dll at runtime.
-Original
Burn created a version type. So if you're creating a Bundle, you use the
v syntax. If we could fix the Windows Installer we would since we're
stuck with string comparisons there (and those don't work perfectly for
version numbers).
On Wed, Jan 30, 2013 at 1:49 PM, Eric Potter
The actual engine executable is ~300 KB. You are likely attaching all your
packages to the executable by leaving things Compressed='yes'. Change the
Bundle/@Compressed attribute to 'no' and you'll see a far smaller
executable (should be under a megabyte).
That is what VS2010 does.
On Wed, Jan
39 matches
Mail list logo
