Another option would be to utilize the new functionality of self-updating
bundles (If you only use a MSI and no bundle, this won't be of use). The core
pull request has been accepted, but WixSDTBA change won't happen in the 3.9
release. If you have a managed BA, it should be relatively trivial
Hi,
Are there any classes around this? P/Invoke is fine if I need to use that.
Cheers
Sean.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 25 June 2014 18:21
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Quick WiX/Dutil query
There's
And DTF wraps it for you.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, June 25, 2014 10:21 AM
To: G
There's a perfectly good Win32 API you can P/Invoke,
MsiInstallProduct(), it's cleaner than firing off a process, waiting,
checking exit codes and other associated process management tasks.
---
Phil Wilson
On Wed, Jun 25, 2014 at 1:56 AM, Sean Farrow
wrote:
> Hi All,
>
> I'm currentl
I've always wondered why that never "cleaned up" properly... In that
case Anton, it sounds as if the users you were having trouble with
either don't have access to %temp% or the PackageCache do to
permission issues.
Carter
Quoting Rob Mensching :
> That C:\c45145141abc stuff is from a rea
I expect you're breaking the update rules:
http://robmensching.com/blog/posts/2007/1/4/doing-a-small-update-or-minor-upgrade-in-msi-use/
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Origin
That C:\c45145141abc stuff is from a really lame bootstrapper from MSFT. Burn
never does that. Burn uses the Temp folder and a secure location called the
"package cache".
___
FireGiant | Dedicated support for the WiX toolset |
http
I am seeing a weird behavior where a feature that was installed locally is
getting set as advertised when a repair or patch is run against the product. I
have never seen this behavior before and have not been able to find a solution
or a cause.
In the installation the features are all set as a
Then again, I could be wrong... :)
Quoting Rob Mensching :
> No.
>
> ___
> FireGiant | Dedicated support for the WiX toolset |
> http://www.firegiant.com/
>
> -Original Message-
> From: Anton Iermolenko [mailto:aiermole...
The Bootstrapper must extract all the files in your Bundles, in your
case the 56 MB's of Files I asked about earlier to a temporary
location before it can execute them or the setup files attached to
them.If the extraction fails, because the temporary location
cannot be written to or cre
No.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Anton Iermolenko [mailto:aiermole...@iopracticeware.com]
Sent: Wednesday, June 25, 2014 7:02 AM
To: General dis
Does Wix Bootstrapper extract something into the directory where Setup.exe
is located?
On Wed, Jun 25, 2014 at 4:49 PM, Carter Young wrote:
> Where are/were you saving the update to? This is a Permissions Issue
> unrelated to WiX. I can say that because of your statement regarding
> the deskt
Where are/were you saving the update to? This is a Permissions Issue
unrelated to WiX. I can say that because of your statement regarding
the desktop:
- Any User will always have full Read/Write Access to their desktop.
This means that whatever Folder you were pushing the update to, the
Was the namespace added to the header of the wxs which uses the
BalExtension.dll elements?
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
If this does not help you may need to post the relevant code from your wxs
file.
--
View this message in context:
http://windows-installer-xml-
Hello Everyone,
I am very new to wix.
I am creating one installer.
I have created two different msi (one 32 and one 64 bit) in wix project.
Now I am creating one bootstrap exe which will run msi depending on
platform.
I have added reference "WixBalExtension.dll" and added both msi as
Msipackage
Hi All,
I'm currently writing an extension to an application in c# that allows a user
to automatically update the application concerned.
Before I call msiexec using the .net Process class, I'm wondering whether Dutil
or WiX have any classes for doing this?
Help appreciated as always.
Kind regar
1. Too many machines it occurred on to be stale user profile.
2. Not sure whether Roaming Profiles are used.
3. No, we download new Setup.exe using our own Updater which then triggers
installation.
We used to do PerMachine MSI installations, but now migrated to Wix
Bootstrapper (with previous inst
Hello,
Let me explain my scenario:
-I upgrage from V1 to V2 of my product using a major upgrade.
V1 has an entirely different upgrade code from V2. You can think that V2
now supersedes V1 and hence is like a different product family altogether.
Neither V1 nor V2 have any transforms embedd
18 matches
Mail list logo
