If I had to guess, it would happen on your machine as well if you renamed the
image after compiling. I don't think you want an absolute path, but rather a
relative one. Then use a Payload element under the BootstrapperApplicationRef
and have Burn compress the image into the bundle.
-Origin
The references you would see about Wix would only be scheduled to run if your
installer is ran with a UI, which by default you won't want to do with burn.
Assuming you are using WixStdBA, take a look at
This should give the user the option of clicking the launch button when the
bundle insta
I'm trying to build a setup program using the Burn bootstrapper (WiX
3.6). I'm changing the theme a bit to get rid of the license screen
and checkbox, and I was hoping to change the icon image in the top
left.
So, in my build directory, I added mytheme.xml, which is basically
just the stock burn
I'm using the WiX (3.6) Burn bootstrapper to bundle a prerequisite
component (Bonjour) with the setup for my program. It works great and
all, but:
I'd like to add a step to the end where I run an executable from my
INSTALLDIR on exit. I'm having a bit of a hard time figuring this out.
I've tried:
It's not only preferred, it's the only way. An application is either logo
compliant or it is not. It's not the job of the installer to mitigate it.
From: "Andy Clugston"
Sent: Tuesday, September 25, 2012 12:49 PM
To: "General discussion for Windows Ins
I am packaging a short cut for each architecture and using an install time
condition to install the appropriate file.
Sent from mobile.
On Sep 25, 2012 2:32 PM, "Hoover, Jacob" wrote:
> A dirty trick would be to have a simple AsAdmin.exe with a manifest that
> blindly executes the source app (sa
Find the GUID for SilverLight 4.0 (easy enough, if it is a MSI user Orca to
locate the ProductCode Property of the msi...
I am checking for MS Sync Framework 2.1 Synchronization, my check is
this(replace to suit SilverLight):
then my pre req check and install if not installed
Update: Digging into the file I discovered/learned some things.
1 - IDs need to match between versions
2 - IDs are case sensitive
3 - Don't go changing the order of files
I got the patch working, but in the end it showed me I need to re-write much of
how we do things. That was a code snippet of
A dirty trick would be to have a simple AsAdmin.exe with a manifest that
blindly executes the source app (same folder).
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: Tuesday, September 25, 2012 12:46 PM
To: General discussion for Windows Installer XML toolset.
S
For this application, no I cannot. I know that is preferred (by me too) but
some of the necessary use cases for this application kills that approach.
On Tue, Sep 25, 2012 at 1:35 PM, Peter Shirtcliffe wrote:
> Could you include a manifest with the application to require elevation/run
> as
> admin
INSTALL.LOG
MSI (s) (F4:0C) [12:08:42:133]: Component:
cmpA65729EDA2FB9E1E1F2E330E73315D53.5559BD7F_840B_4DBA_8D43_1A50B01331DC;
Installed: Absent; Request: Local; Action: Local; Client State: Unknown
UNINSTALL.LOG
MSI (s) (B0:B8) [12:46:06:210]: Component:
cmpA65729EDA2FB9E1E1F2E330E7331
Could you include a manifest with the application to require elevation/run as
admin privileges ?
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: 25 September 2012 18:23
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Shortcut Element
What is the action state for the Component
"cmpA65729EDA2FB9E1E1F2E330E73315D53"? Search the log for the component by
that name and it's Guid. You'll find more useful information since the
Windows Installer bases all of it's calculations on Component states.
On Tue, Sep 25, 2012 at 7:53 AM, Steve
I want to create a shortcut to point to my executable. The shortcut will be
used in cases where the .exe needs to run with elevate privileges. I don't
see any attribute(s) in the schema that can allow me to create the shortcut
with this flag.
So, is it up to me to deliver the .LNK file myself? Nee
Has anyone figured out how to check to see if Silverlight 4.0 has been
installed from within a Burn Bundle?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat
When I use name I get:
LGHT0103: The system cannot find the file 'D:\Folder1\Folder2 '
Note: It does mention the filename.
Neil
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 25 September 2012 17:26
To: General discussion for Windows Installer XML tool
I think if you specify a Source attribute at all, it overrides anything from
parent elements. Try changing "Source" to "Name".
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 25 September 2012 16:46
To: General toolset. (wix-users@lists.sourceforge.net)
Subject
I am trying to use the ComponentGroup/@Source to set the source path for some
components but it is not working, the syntax I am using is:
I would expect that to find Dummy.exe in the path "$(var.SolutionDir)output"
but it fails with a the error:
LGHT0103: The sy
Hi all,
i found a solution to my problem using heat on JRE installer and adding to
my ExePackage
Thanks again!
2012/9/25 Pasquale Fersini
> Many many many thanks, guys. You saved me a lot a time!
> No way to do same thing for java installer?
>
>
> 2012/9/25 Rob Mensching
>
>> I think you ne
Okay here is the code for the component:
*Here is the Install log info:*
MSI (s) (88:E8) [10:37:34:121]: Executing op:
ComponentRegister(ComponentId={4C857562-218B-48E5-9635-41689CE2ADDC},KeyPath=C:\Program
Files
(x86)\Titus\Gloria\AdminConsole\bin\Newtonsoft.Json.dll,St
This worked! Thanks!!!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, September 24, 2012 6:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating an uninstall shortcut
The code here worked:
http://robmenschi
Just to update I have found that the problem seems to stem from the torch call
and if I use the wixmst file generated by 3.5 it creates the patch fine.
Here is my torch call:
"%WIXDIR%\torch.exe" -p -xi "%PatchSourse%PROGRAMx32.wixpdb"
%NewInstall%x86\PROGRAMx32.wixpdb -out %OutputFolder%\PROGR
When a keypath attribute is not explicitly specified, the first file or
registry key in the component is used, but this is not recommended.
Do those code snippets show the whole of the components ? You can't change
the contents of a component once it's been released. That's a violation of
the compo
I tried searching Google and the archive, but I don't have a clear
answer/understanding of why I am getting this error:
error PYRO0243 : Component <> has a changed keypath
I am trying to create a patch using the base version of a full install against
a REL 2. According to some accounts, this o
Did you have any more luck with this issue Leo?
I have the same problem after upgrading to Wix 3.6, nothing has changed, I
still have the same patch family. In 3.5 it picks up the fact that the
versions have changed on multiple files and adds them to the patch however
in 3.6 it comes up with the e
I assume your non-Wix setup is still an MSI.
The FindRelatedProducts action that uses the Upgrade table cannot detect
products installed for a different context. i.e. Your per-machine installer
can't see a per-user installer using Upgrade elements. You could use upgrade
elements to detect an exist
Hi I am trying to do two custom actions when a certain button is clicked but
the second is never getting executed. Can anyone tell me what I am doing
wrong?
1
1
Kind Regards,
Natalie Carr
-
If the payloads weren't laid out correctly, shouldn't selecting the language
explicitly via -lang fail as well (as I wrote, this works perfectly)?
Since the official WiX documentation describes localizing the standard
bootstrapper application rather sparsely, the layout may be indeed not correct
I would like to use WiX to install a device metadata package. This needs to go
into a sub-folder of a folder identified by a KNOWNFOLDERID (specifically
FOLDERID_DeviceMetadataStore)
The same question was asked back in 2009 (
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Instal
Hello folks,
as I have to implement an installer with WiX and burn, that must handle
updates, I try to figure out, how the windows installer concepts for those
tasks functions and how to set up a nice architecture around this. As I have no
experience with this yet, I do not want to construct an
Many many many thanks, guys. You saved me a lot a time!
No way to do same thing for java installer?
2012/9/25 Rob Mensching
> I think you need Protocol='netfx' on the ExePackage. Built in
> PackageGroupRef for NETFX in WiX does this, IIRC.
>
> On Mon, Sep 24, 2012 at 8:36 AM, Pasquale Fersini <
31 matches
Mail list logo
