Hi Don,
The main feature of WI 4.5 that I found to be the most useful was Transactions,
but this is only really an issue if you have a multi package installation.
The best option that I am aware of would be to give the customer the chance to
take care of the deficiency beforehand. Document it s
Hi,
I had a few problems with the new Wix Toolset RC, so I decided to reinstall
it, but it keeps failing. I tried to copy paste the links into my browser
and got Network error. Does anyone know when it's gonna get fixed
//Caisa
[06CC:0150][2012-06-13T08:04:36]: Apply begin
[0B00:0780][2012
Hi Matt!
You mean like this?
This is the way I have it today, and both files are copied to the same
package cache folder, but since the installation process of the exe isn't
started from that folder it's not going to find the text file. The process
is started from the path w
On 12-Jun-12 11:55, Miss Parker wrote:
> If I do that, then .Net 4.0 won't get installed before the BA GUI starts. Or
> am I missing something? I tried to put both 3.5 and 4 in the Package group
> that's connected to WixMbaPrereqPackageId, but it just crashed.
What crashed? What does the log say?
I am not sure exactly how to do this, but you should be able to do what you
want by caching the exe payload, and having the text file in the same payload.
I know that this is done for MSI files and external cabs, so the engine
supports it. But I am not sure of what the syntax would be. I thin
Yes - Variable: WixBundleElevated = 1
Could it be that UAC is disabled therefore it is elevated but it actually needs
to be an administrator as well?
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 12 June 2012 20:36
To: wix-users@lists.sourceforge.net
Subje
On 12-Jun-12 12:15, Neil Sleightholm wrote:
> Comparing the logs it looks like burn is not doing the elevate step.
Is WixBundleElevated set?
--
sig://boB
http://joyofsetup.com/
--
Live Security Virtual Conference
Excl
> -Original Message-
> From: Don Walker [mailto:don.wal...@versaterm.com]
> Sent: Tuesday, June 12, 2012 15:56
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Windows Installer 3.1 or 4.5 for XP?
>
> I'm likely to be supporting installs on Windows XP until past the MS end
of
>
Hi,
It's down to the architecture of your software and the needs of your users.
Typically you only offer the correct msi per bitness as for most people there
is no reason to have both.
If you have a lot of plugin developers that will be struggling to keep up and
make 64bit versions for your softwar
It looks like it has something to do with permissions/uac.
If I create a guest user on a Win7 machine and run the package then I get a
prompt to say I need to provide an admin user and if I do it installs ok. On
the PC with the issue it is a member of the domain and I have logon rights but
not
I'm likely to be supporting installs on Windows XP until past the MS end of
support date. Most of our customers running XP most likely have Windows
Installer 3.1 installed. As far as I can tell, upgrading to Windows Installer
4.5 will force a reboot. Should I require Windows 4.5 anyway?
I have
If I do that, then .Net 4.0 won't get installed before the BA GUI starts. Or
am I missing something? I tried to put both 3.5 and 4 in the Package group
that's connected to WixMbaPrereqPackageId, but it just crashed.
But thanks anyway!
//Caisa
--
View this message in context:
http://windows-inst
That would work if I had any sort of control over the exe, but I don't.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Exe-package-can-t-find-payload-file-that-s-not-a-dll-tp7578750p7578783.html
Sent from the wix-users mailing list archive at
Hi,
I upgraded to Wix Toolset RC today, and suddenly some MsiPackage elements in
my bundle generated an error: "Value cannot be null" (Light.exe) There are
absolutely nothing special about the packages, and there were no problems
building the BA before the upgrade.
Does anyone know what causes t
I don't have an answer for you, but I got a similar error (the registration
errors) during uninstall and that caused the uninstall to fail. It would be
nice to know what's causing this.
//Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Fa
Thanks for your input Daniel. I all ready have two seperate MSIs for each
bitage, and they currently share a ProductGUID to prevent any user
installing both, but I'm wondering if this should not be the case and that
users should be allowed to install both - as seems necessary fot photo
editing apps
There's this, not official but useful...
http://blogs.msdn.com/b/oldnewthing/archive/2007/09/17/4948130.aspx
Phil W
From: Jerra [beddel...@gmail.com]
Sent: Tuesday, June 12, 2012 12:22 AM
To: General discussion for Windows Installer XML toolset.
Subject:
A couple of burn packages built with v3.6.2928.0 are failing on one PC with the
following error:
[0B88:1E3C][2012-06-12T11:19:38]: Plan complete, result: 0x0
[0B88:1E3C][2012-06-12T11:19:38]: Apply begin
[174C:1F10][2012-06-12T11:19:38]: Automatic updates could not be paused due to
error: 0x8007
Hello Gareth,
I am not an expert on installation but I use WiX to install both 32-bit and
64-bit components on a 64-bit machine using a single installer and it has been
working fine for me. In fact, since our "application" is essentially a plugin
for a third-party application that comes in both
When I first looked into creating a 64-bit package to sit alongside our
existing 32-bit package it seemed obvious to me that you should offer one or
the other, which ever is appropriate for the user's OS. And most of what
I've read supports this.
However, Adobe PhotoShop offer the option to instal
I'm a developer, not an IT guy too, so it's not anything I've ever done, just
read about :)
Yes, login scripts are similar to start-up scripts but run during login,
rather than computer start up. I guess youd use a startup script for a
per-machine MSI and a login script for a per-user MSI. You assi
I want to harvest a reg file using heat. The wxs file is generated using:
heat reg data.reg" -ag -sfrag -cg Registry -o Registry.wxs
The call to heat succeeds but when I build the installer the following error
message occurs:
Registry.wxs (4): The Directory element requires the Name attribute b
OK thanks! Well installation is sort of a gigantic big black hole I am
trying to understand. Luckily there is a lot of info on the web
regarding WiX and this mailing list.
MS guidelines, I haven't seen any of those though..
> System preferences... Now that's a different beast :)
I do not under
Refer the ms guidelines, user data should remain after uninstall. So leaving a
trail that is expected.
System preferences... Now that's a different beast :)
Cheers,
Sascha
On 11/06/2012, at 11:52 PM, Jerra wrote:
> In my application I use the built in functionality for storing user settings
24 matches
Mail list logo
