That's another feature I'm hoping to implement: Burn should support 'Modifying'
the installation, displaying the options page during maintenance.
--
Bruce
Sent from my iPhone
On 16 Sep 2013, at 15:59, Steven Ogilvie steven.ogil...@titus.com wrote:
Did I send you updated code?
Different
Hi,
Thanks for the tips. I'm still confused ..
The tutorial link you suggested says ..
Step 1: Create a bundle for your application
Follow the instructions in Building Installation Package Bundles
Step 2: Add a reference to one of the .Net PackageGroups
Add a reference to WixNetFxExtension to
How to create BootStrapper (EXE) file will show only Internal MSI UI's only?
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
Hi Rob and others on the mailing list!
I'm wondering the same thing. I have a minimal UI msi that I've customised
slightly with logos and banners. I want this UI to run immediately instead
of the first screen that the botstrapper UI shows. (licence agreement, etc).
The licence agreement gets
So it is not currently supported?
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: September-18-13 3:15 AM
To: General discussion for Windows Installer XML toolset.
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add text to final
On 18/09/2013 14:08, Steven Ogilvie wrote:
So it is not currently supported?
I don't think so. At least, the WixStdBA doesn't.
--
Bruce Cran
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
Yes. You'd need to create a custom BA.
On Wed, Sep 18, 2013 at 2:27 AM, nkshirsagar nkshirsa...@gmail.com wrote:
Hi Rob and others on the mailing list!
I'm wondering the same thing. I have a minimal UI msi that I've customised
slightly with logos and banners. I want this UI to run
There seems to be a lot of demand for more control over installer and
bootstrapper UIs. Just out of curiosity, is this being worked on for future WiX
releases?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, September 18, 2013 12:27
To: General
I believe the mantra is don't use installer UI's, use a BA UI. As such, if
you need a custom UI then generate a BA to give the look and feel that you
want. The reasoning behind having a BA UI is so you can have a single unified
installation experience. Having a chain of 5 MSI's all exposing
It just seems like going from the stock BA to rolling your own custom BA just
to either get rid of the UI or add a single text box, radio button, or
window/step seems extremely costly in time and effort for what seems like a
minor modification.
-Original Message-
From: Hoover, Jacob
PackageGroupRef Id=NetFx45Web/ will reference dotNetFx45_Full_setup.exe
in your redist folder, and if it isn't there it will download it from
Microsoft's servers (@ http://go.microsoft.com/fwlink/?LinkId=225704). All of
that is in WixNetFxExtension already written for you.
The Product.wxs
Please do not use a custom action to run the install if that other product is
MSI-based. Add it to your Upgrade table and remove it that way.
Date: Tue, 17 Sep 2013 17:56:44 -0700
From: jack.sojo...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Detecting a different
Be aware that if your custom action gets any properties, then you'll need
to push those through by using CustomActionData.
On 18 September 2013 19:07, Phil Wilson phildgwil...@gmail.com wrote:
Your copy custom action is immediate - that means it will always happen
before any files are
I believe there is already a bug open about this issue. MPF and
Configuration editing don't seem to get along... or something like that.
It's Votive. shrug/
On Wed, Sep 18, 2013 at 11:10 AM, Blair Murri os...@live.com wrote:
I would think that that should just work. Please file a bug.
From:
Looping wix-users back into the conversation.
From: os...@live.com
To: jack.sojo...@gmail.com
Subject: RE: [WiX-users] Detecting a different product install
Date: Wed, 18 Sep 2013 12:19:23 -0700
Add this to what you already have:
Upgrade Id=theirupgradecode guid
UpgradeVersion Minimum=0
The stock BA is open source. You don't need to start from scratch,
just modify the stock one.
--
Nicolás
2013/9/18 Alain Forget afor...@cmu.edu:
It just seems like going from the stock BA to rolling your own custom BA just
to either get rid of the UI or add a single text box, radio button,
Is there a tutorial somewhere on where to get the stock BA's source, and how to
make various changes to it? The only tutorial I found involved cracking open
Visual Studio, and seemed to involve recompiling the whole source and...yeah, a
big hurdle to jump.
-Original Message-
From:
It's a totally different product. I just want to remove it if its
installed. My upgrade table looks like this...
Upgrade Id=myupgradecode guid
UpgradeVersion Minimum=1.0.0
Maximum=$(var.MAXVERSION)
IncludeMinimum=yes
IncludeMaximum=yes
OnlyDetect=no
Your copy custom action is immediate - that means it will always happen
before any files are actually copied. If you need it to run after
InstallFiles has physically copied files it should be marked deferred.
Phil Wilson
On Tue, Sep 17, 2013 at 10:45 PM, Kai Peters kpet...@otaksoft.com wrote:
I would think that that should just work. Please file a bug.
From: mri...@realtyim.com
To: wix-users@lists.sourceforge.net
Date: Tue, 17 Sep 2013 22:53:18 +
Subject: Re: [WiX-users] Changing configuration and/or platform in solution -
Configuration Manger does nothing
I'm not sure
I thought so to, but I couldn't find it.
From: r...@robmensching.com
Date: Wed, 18 Sep 2013 11:44:39 -0700
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [SPAM] Re: Changing configuration and/or platform in
solution - Configuration Manger does nothing
I believe there is
On my 5 year old machine it takes 5 minutes to build all of the WiX toolset
source. That isn't *that* long is it? Seems like a reasonable amount of
time to build a project of our size. There is documentation in the WiX.chm
with instructions how to build.
On Wed, Sep 18, 2013 at 12:29 PM, Alain
...and be sure to publish your changes because the code is weak copyleft
open source.
On Wed, Sep 18, 2013 at 12:25 PM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
The stock BA is open source. You don't need to start from scratch,
just modify the stock one.
--
Nicolás
2013/9/18
Is there some reason you can't do a major upgrade to remove it? If you know
its UpgradeCode you can get it uninstalled.
Phil Wilson
On Tue, Sep 17, 2013 at 5:56 PM, Jack Sojourn jack.sojo...@gmail.comwrote:
Hello...I need to detect if a totally different product is installed and if
so
I don't mean compile and setup time. I mean time and effort for someone
completely unfamiliar with the WiX source and whatever may be involved in
rolling a custom bootstrapper (like myself and most other people on here who
ask how to do what doesn't seem like a complex request).
Sure, for you
The MSP is for Office/Word and not your add-in, correct?
If so, you will need to bootstrap the MSP from outside of your MSI (there
aren't many good ways to do so from within your MSI). Most on this list would
likely suggest using Burn (now part of WiX).
Date: Tue, 17 Sep 2013 20:10:46 +0200
It's not trivial to create a custom BA. It takes time and effort.
On Wed, Sep 18, 2013 at 12:51 PM, Alain Forget afor...@cmu.edu wrote:
I don't mean compile and setup time. I mean time and effort for someone
completely unfamiliar with the WiX source and whatever may be involved in
rolling a
Alain,
One thing you have to remember, this is a FREE product.
It is not a full time job for the main developers, they do this on their
spare time and other developers add stuff on their spare time as well.
Burn/Boostrapper was added in 3.6 (or was it 3.5) as add on tool for WIX and is
an
2013/9/18 Vadivel Natarajan vadiv...@syncfusion.com:
We need to fix this error immediately. This is very urgent. Can someone
please help?
http://www.catb.org/esr/faqs/smart-questions.html#urgent
--
Nicolás
--
As far as I know, suppressing the Burn UI and using only the MSI UI is
not how Burn is *supposed* to be used. Why would the WiX developers
spend time and effort to make it easier to use in that way?
--
Nicolás
2013/9/18 Alain Forget afor...@cmu.edu:
Which I think reinforces my point. It's not
I understand it's FREE, but I've gotten the sense that at least some WiX
developers care to make WiX not only great for themselves, but great for
everyone, and encourage its use. If so, then the fewer barriers there are to
accomplish WiX users' goals, the more people will use it, and
I disagree. What it says that you think one or more people need to
volunteer to add even *more* functionality to what has been provided by
volunteers up to this point.
Let me suggest that telling the people that have spent significant amount
of effort getting the WiX toolset to this point that
I thinks it's learning to use the API of C++ burn that’s the hurdle.
Especially since an installer is fairly important to get right. I've been
putting off creating a custom BA because of lack of docs.Eventually I will
and at that time I can provide a tutorial if it's still useful. Even
Minor changes = adding a text field, a check box, a window in the wizard steps,
something like that. I never figured out how to do that without needing a
custom BA, at which point, I gave up (thankfully, because apparently it's very
time and effort intensive!).
-Original Message-
From:
What do you mean by minor changes? I do that using the stdba by changing the
templates. But my minor changes are adding graphics, adding installer
version, changing text size, etc.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: September-18-13 5:02 PM
To:
Wow. My sincere apologies, Rob. I was just adding food for thought. I think the
easier WiX can be for everyone to accomplish their goals, the more people will
use it, and contribute to it, making it even better. I wasn't at all trying to
say that WiX is bunk because it doesn't do this one
Note: I don't know that all the developers on the WiX toolset believe that
Burn based installs should display single unified UI by suppressing
internal MSI UI, but I do.
However, Burn certainly supports showing internal MSI UI. In fact, in
v3.8 FireGiant found and fixed a bug related to showing
Which I think reinforces my point. It's not clear to me why it needs to take
lots of time and effort just to suppress a UI, or make minor changes to an
existing UI.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, September 18, 2013 15:58
To:
Alain,
You can't expect someone to hold your hand!
You have to dive in, figure out the code, and try to add some stuff to it,
trial and error, and by doing this you are gaining knowledge on how the code
works...
As Wesley stated you can change minor things by the theme wxl/xml files
But what
Awesome Rob, I logged that Internal MSI UI and the progress not moving bug,
glad its fixed I will look forward to 3.8 :)
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: September-18-13 4:41 PM
To: General discussion for Windows Installer XML toolset.
Subject:
You can do a text field/check box using Niel's wixstba if using 3.7, it's in
3.8 I believe. A new window needs a custom BA.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: September-18-13 5:35 PM
To: Wesley Manning; 'General discussion for Windows Installer XML
I was able to add checkboxes/radiobuttons on Welcome Page, then fool
WixExtendedBA to think the Options button was Next and the options page to
be the rich text EULA page, so I have 2 pages now... select the product to
install, click next agree to the EULA and click Install, most of that was
You have to dive in, figure out the code, and try to add some stuff to it,
trial and error, and by doing this you are gaining knowledge on how the code
works...
Sorry, but I don't believe in that. Part of my background is in usability, so
my view is that, if to accomplish anything at all,
Wow, what black magic is this? :-P Somehow I completely failed to do something
similar in the theme files a few weeks ago. If I need to tackle it again, I
hope you won't mind if I ask for advice.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Wednesday,
Thanks, Steve!
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Wednesday, September 18, 2013 17:15
To: afor...@cmu.edu; 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less?
I am
You can write BA's in managed code too. The WixBA is managed (available in
the WiX tree) as is the Visual Studio BA (obviously, not available).
On Wed, Sep 18, 2013 at 1:19 PM, Wesley Manning wmann...@dynagen.ca wrote:
I thinks it's learning to use the API of C++ burn that’s the hurdle.
I am using Neil's WixExtendedBA which is not part of Wix 3.7 (it is in Wix 3.8)
You can get it from: https://wixextba.codeplex.com/ for this you need to
customize your theme files xml/wxl
i.e.
HyperLinkTheme.xml
Page Name=Install
Text X=11 Y=80 Width=-11 Height=30 FontId=2
On 9/18/13 1:57 PM, Alain Forget wrote:
Gaining knowledge on how code works is fine and has value, but at the end of
the day, people have primary tasks they're trying to get done and can't
always commit the time or effort into tangential secondary tasks.
I think it is clear that the WiX
My mistake for not specifying what else I had tried:
When i switched to 'deferred' LIGHT complained:
error LGHT0204 : ICE77: CA_CopyMasterIni is a in-script custom action. It must
be sequenced in
between the InstallInitialize action and the InstallFinalize action in the
InstallExecuteSequence
49 matches
Mail list logo
