Alright, I tried a different install command according to an example I found
in the forum:
ExePackage Id=Update SuppressSignatureVerification=yes
SourceFile=C:\Downloads\Update_1.12.10.exe PerMachine=yes
InstallCommand=/qn UninstallCommand=/qn Vital=no/
It didn't work for me
Did you reference anything inside the fragment from your main MSI ? If not,
see Fragment in the wix help file.
-Original Message-
From: E. Timothy Uy [mailto:t...@loqu8.com]
Sent: 25 April 2012 00:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
See Util:CloseApplication in the wix help.
-Original Message-
From: E. Timothy Uy [mailto:t...@loqu8.com]
Sent: 25 April 2012 06:00
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] killing Chrome and Firefox
Hi, we are a requirement to kill Chrome and
Hi -
I have set protocol=netfx for the .Net 4.0 ExePackage, and i do get a
moving progress bar during its installation. However i wonder if there is a
way of showing what the .net installer is actually doing because this can
take ages still looks at times like it has hung.
I use
Got this working using the steps outlined at
http://wix.sourceforge.net/manual-wix3/insignia.htm
Target Name=SignBundleEngine
Exec Command=quot;C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\bin\signtool.exequot; sign /f privatekey.pfx /p mypassword
/t
More problems with this. This time with MspPackage (code as previous). The
issue is with a system which has already had the MSP applied.
[1428:145C][2012-04-25T14:45:28]: Setting version variable
'SharedContentVersion' to value '2.2.0.0'
[1428:145C][2012-04-25T14:45:29]: Detected package:
Upgraded from WiX v3.6.2816 to v3.6.2823. Haven't changed anything in source.
MSI's build fine but my burn bundle fails now. Log is as follows:
-- Rebuild All started: Project: VESetup, Configuration: Release x86 --
Deleting file obj\Release\Bundle.wixobj.
Unfortunately, that is a feature request you need to send to the NETFX
team. We are getting everything we can out of the netfx protocol.
On Wed, Apr 25, 2012 at 4:57 AM, stewarth stewart.hil...@thomsonreuters.com
wrote:
Hi -
I have set protocol=netfx for the .Net 4.0 ExePackage, and i do get
It very much depends how you structure your .wxs code.
On Tue, Apr 24, 2012 at 4:53 PM, E. Timothy Uy t...@loqu8.com wrote:
Thanks Rob! I added
?xml version=1.0 encoding=utf-8?
WixLocalization Culture=en-us xmlns=
http://schemas.microsoft.com/wix/2006/localization;
String Id=Error1703[2]
On 25-Apr-12 10:06, Pally Sandher wrote:
Why is it attempting to uninstall the patch when the condition is false the
patch has AllowRemoval=no?
Because Burn always attempts to uninstall a package that's present when
its install condition is false, and Burn doesn't know the patch is
On 25-Apr-12 11:45, Pally Sandher wrote:
Microsoft (R) Windows Installer Xml Linker version 3.6.2823.0
Copyright (C) Microsoft Corporation. All rights reserved.
light.exe(0,0): error LGHT0001: An item with the same key has already been
added.
Define your directory like this:
Directory Id=WEBSITEDIRNAME
And don't create a property for WEBSITEDIRNAME.
Essentially all directory ids behave like properties. Since you need to change
the directory with a control that requires a public property so the directory
id must be all uppercase.
Looks like I can only use WixCloseApplications once. How do I close all
browsers both before installation and right before uninstallation? Trying
the following...
util:CloseApplication Id=CloseIE CloseMessage=no
Description=Internet Explorer is still
running.
By the way, the code below doesn't work at all.
On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy t...@loqu8.com wrote:
Looks like I can only use WixCloseApplications once. How do I close all
browsers both before installation and right before uninstallation? Trying
the following...
Ahh, I'm sure that was it. A Fragment that does not get referenced does not
got run correct?
On Wed, Apr 25, 2012 at 1:50 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
Did you reference anything inside the fragment from your main MSI ? If not,
see Fragment in the wix help file.
I changed WixCloseApplications to run before InstallInitialize but this did
not help either. From the .msi log, I see
Action 12:12:49: WixCloseApplications.
Action start 12:12:49: WixCloseApplications.
Action ended 12:12:50: WixCloseApplications. Return value 1.
Action 12:12:50:
Run wouldn't be the proper term. It's more including the fragment when
it compiles the MSI. If it isn't referenced, then it doesn't exist.
-Original Message-
From: E. Timothy Uy [mailto:t...@loqu8.com]
Sent: Wednesday, April 25, 2012 2:15 PM
To: General discussion for Windows Installer
Silly me. I was able to get the browsers to close by setting
CloseMessage=yes. Next step, how do I use FilesInUse?
On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy t...@loqu8.com wrote:
I changed WixCloseApplications to run before InstallInitialize but this
did not help either. From the .msi
On 25/04/2012 20:33, Hoover, Jacob wrote:
Run wouldn't be the proper term. It's more including the fragment when
it compiles the MSI. If it isn't referenced, then it doesn't exist.
I don't think 'compile' is the proper term either - I think it happens
during linking :)
--
Bruce Cran
Dear Rob et al.,
Thanks everyone for being so gracious. This time I would like the installer
to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and
restart them after installation completes. I think I should
use MsiRMFilesInUse but have not been able to locate any samples or
Looks like RM only works with Vista+. What is the fallback for XP?
On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy t...@loqu8.com wrote:
Dear Rob et al.,
Thanks everyone for being so gracious. This time I would like the
installer to shutdown any browsers (IE, Chrome, Firefox) prior to
I was able to show the FilesInUse (for iexplore, chrome and firefox) but
just adding
util:RestartResource Id=RestartIE ProcessName=iexplore.exe /
util:RestartResource Id=RestartChrome ProcessName=chrome.exe /
util:RestartResource Id=RestartFirefox ProcessName=firefox.exe /
However,
The plot thickens. Removing Chrome from the mix makes it work.
util:RestartResource Id=RestartIE ProcessName=iexplore.exe /
util:RestartResource Id=RestartFirefox ProcessName=firefox.exe /
Is this solvable? I did notice that chrome.exe uses a lot of processes.
Could this be the issue? Is there a
chrome.exe - does not close
firefox.exe - closes, but never restarts
iexplore.exe - closes and restarts (blank page)
On Wed, Apr 25, 2012 at 2:50 PM, E. Timothy Uy t...@loqu8.com wrote:
The plot thickens. Removing Chrome from the mix makes it work.
util:RestartResource Id=RestartIE
It seems that CloseMessage=no should have triggered FilesInUse, but it
doesn't at all. The installation just proceeds.
On Wed, Apr 25, 2012 at 1:05 PM, E. Timothy Uy t...@loqu8.com wrote:
Silly me. I was able to get the browsers to close by setting
CloseMessage=yes. Next step, how do I use
A long time ago our company released a product, let's call it Product
1.0. A little while later we released an add-on, let's call it Add-On
1.0.
Now we are releasing Product 1.5. However we decided that for this
version Add-On 1.5 would be a subfeature of Product 1.5 rather than a
separate
Hi,
I have created a bootstrapper (using burn in visual studio 2010) which
installs .Net framework4 as prerequisite and then installs the actual
msi. Following are the problem that I am facing and I really need your help
to resolve those problems.
1 I don't want the bootstrapper to have an entry
Sounds like you are using an old version. Upgrade to latest build for all
that to work.
On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul ani.banti.24...@gmail.comwrote:
Hi,
I have created a bootstrapper (using burn in visual studio 2010) which
installs .Net framework4 as prerequisite and then
Ok I shall try that and get back to you.
But let me know the wix variable names that are used to set bootstrapper
dialog title and bootstrapper dialog icon.
On Thu, Apr 26, 2012 at 10:53 AM, Rob Mensching r...@robmensching.comwrote:
Sounds like you are using an old version. Upgrade to latest
Very hard to tell. It very much depends on how the executable works. Burn
just launches the executable and passes the appropriate command-line
(InstallCommand for install and UninstallCommand for uninstall and
RepairCommand for repair).
On Wed, Apr 25, 2012 at 12:18 AM, Miss Parker
I wouldn't do 3. It just sounds messy. You could also consider shipping a
patch for Add-on 1.0 to fix it.
PS: This is why you should always ship an upgrade of your v1 product before
you ship v1. smile/
On Wed, Apr 25, 2012 at 5:03 PM, Daetrin Ungashak gfin...@gmail.com wrote:
A long time ago
Yeah well, apparently a simple /s sufficed. I tried that before of course,
but probably in combination with something else, which made the silent
install fail.
Thank you all for your input, I learn more and more about Burn everyday. :)
--
View this message in context:
Sounds like we should scan patches for those that disallow removal and mark
them permanent.
The InstallCondition behavior is expected. If the InstallCondition is false
that means this Package should not be Installed (aka: should not exist on
the box).
On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson
Instead of using a hard coded Custom/@Sequence number can you use a
relative Before/After to ensure the action executes before the UI shows up.
Otherwise, look in a verbose log file and see that the Property is getting
set correctly before it is used.
On Tue, Apr 24, 2012 at 6:39 AM, Ravi Raj
I did lots of work was done in WiX v3.6 to get this scenario fixed to work
as you describe at the end. What version of the WiX toolset are you using?
On Fri, Apr 20, 2012 at 1:56 PM, Abbott, Brian (GE Energy)
brian.abb...@ge.com wrote:
I'm trying to use wix to build an installer for
35 matches
Mail list logo
