Could you provide this again Jacob? I'm having trouble writing this wrapper
with C#. If you could point me in the right direction that would be great.
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-auto-update-like-ClickOnce-in-WIX-
You may find this useful:
http://robmensching.com/blog/posts/2007/1/4/doing-a-small-update-or-minor-upgrade-in-msi-use/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Sasc
I figured it out, it was never about Config.msi in the first place. When I
looked at the log file for a successful upgrade I realized it has the same
Config.msi error message in it, so that's always there and probably also
the reason why the installer isn't actually failing, I guess MSI just
ignore
Classification: Public
Why are you reinventing the wheel? Burn already has a "button" to launch
applications on the finish dialog, it is not a checkbox but a button:
http://wixtoolset.org/documentation/manual/v3/xsd/bal/wixstandardbootstrapperapplication.html
http://windows-installer-xml-wix-too
Okay I was able to generate a check box field at the end of the bootstrapper,
but now I need to know how it actually gets triggered to launch the app?
Here is what I have in the theme file:
#(loc.SuccessHeader)
#(loc.LaunchAppCheckbox)
#(loc.OptionsOkButton)
#
Maybe wix3\src\ext\BalExtension\wixstdba\Resources + thmviewer.exe?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Fri
I thought when it uninstalls the old version it does so by running the
cached MSI for THAT version, which also doesn't have CONFIGFOLDER in it?
I've made other changes to the installer before such as adding new files
etc. and I've never had issues like this.
// Sascha
On Fri, Sep 5, 2014 at 12:
Thanks Rob...
Since I have not yet had to do any Burn customization is there any samples
that would help me get started on how to customizing the
BootstrapperApplication?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-built-in-varia
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling,
repairing a few dinky products we have built installers for over the last
while. Even added a new one with a large (100 megabytes uncompressed) payload.
Tried with and without UAC for all. No troubles at all with the trou
Thanks Rob.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-can-I-display-Maintenance-Dialog-of-MSI-using-burn-bootstrapper-tp7596679p7596683.html
Sent from the wix-users mailing list archive at Nabble.com.
Custom BootstrapperApplication could do that.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, September 5, 2014
Correct. There is a feature request open to try to figure out how to support it
(non-trivial problem).
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Getye Tesfay
For wixstdba you can customize the theme file. You could also create a custom
BootstrapperApplication.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: TimM [mailto
I have MSI which is Launched by burn bootstrapper, but I could not be able to
display the Maintenance dialog from burn.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_
Ok, so CONFIGFOLDER is not going to exist on the old installer. What is you
upgrade scheduling? To make this work, you probably need
MajorUpgrade@Schdule=afterInstallInitialize or afterInstallValidate. In an
overlapped upgrade, it's going to attempt to remove a non-existent CONFIGFOLDER.
--
As I said it's really simple, here an excerpt from my directory definitions
(all within the same Fragment):
1
2
3
4
In the old installer lines 1, 2, and 4 existed already, in the new version
I added line 3. The WiX properties are defined at the top of the file right
bel
There are a bunch of Burn built-in variables that we can use, but if what I
want is not included in that list then how can I go about declaring a new
variable that gets a standard environment variable?
Basically what I need is to get the %USERDNSDOMAIN and %USERDOMAIN
environment variables and app
The database being referred to is probably the MSI itself. Problems with
RemoveFolder usually occur when the property is not defined soon enough. It
must be defined before the RemoveFolders standard action runs.
What does your authoring look like? Are you using a property?
--
John Merryweath
Yes this all works and all, but is there no way that we can have say some
text with a description of what will be launched?
I have a WiX .msi installer that contains all the standard and custom UI
that we need and it contains the check box at the end of the install for the
user to launch our admin
No, there is no database involved in the installer. I get that the error
isn't really about the Config.msi directory, but I don't know how to solve
this.
As I said, my changes that caused this failure are trivial, a new directory
and matching RemoveFolder entry, neither of which should cause this?
Message 1:
Error 2228 = Database: [2]. Unknown table '[3]' in SQL query: [4].
Error 2911 = Could not remove the folder [2].
Message 2:
Error 2318 = File does not exist: [2].
Did you happen to add a Database Table in your update. I can't tell
if Message 1 is coming from the Installer Tables or
That was an approach I wasn't expecting. While this may work in the
short term, if you start adding items to your WiX project that need
the eventsmapping table, you may run into issues.
Quoting Max Paschetto :
> Sorry for the (no subject) topic.
>
> I took the Orca way and deleting the Event
Sorry for the (no subject) topic.
I took the Orca way and deleting the EventMapping table solved my
issue, thank you.
Actually I generate the msm with the Deployment Wizard.
Didn't tried the bootstrapper way, I'll try to remember this option
for the next time.
---
Thx John / David .. good to know that someone is already using it on Win
2012/8/8.1
After a bit more research , its actually the MSIUSEREALADMINDETECTION
property that does not seem to work to good on Windows 8.1 (for a local
administrator user) ...
I will remove this property and try again t
I ran into a weird issue that I can't seem to figure out, hopefully someone
has an idea.
My issue happens only when doing a minor upgrade from an older version to a
newer version of my product. The failure lines from the log look like this:
MSI (s) (1C:3C) [23:17:21:084]: Note: 1: 2228 2: 3: Err
25 matches
Mail list logo
