Please refer to the immediately previous post:
https://sourceforge.net/mailarchive/message.php?msg_id=30340537
Sorry folks - I neglected to include the Bundle.WXS file:
~ Shaun
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
What I want my bootstrapper to do is chain together a few simple installs
and install on Windows XP.
1. Dot net framwork 4.0 full (dotNetFx40_Full_x86_x64.exe)
2. Crystal Reports runtime 32-bit (CRRuntime_32bit_13_0_4.msi)
3. My custom MSI (created by WiX) which works fine.
I'm still curious how you are calling CM_Reenumerate_DevNode on the root
devnode in your custom
action.
Would you mind sharing this snippet?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/DIFxApp-and-upgrades-tp5786223p7582858.html
Sent from the
You are correct on pretty much all accounts. It's a space that needs more
development to get really good.
On Fri, Jan 11, 2013 at 2:00 PM, Nicholas Devenish wrote:
> I'm writing the installation for a software package, and want to use the
> features selection to do so, and have it mostly running
We haven't created a 64-bit Burn since 32-bit works everywhere today. That
will change in the future I expect (if Server Core catches on).
On Fri, Jan 11, 2013 at 2:04 PM, ptr wrote:
> Thanks Jacob, I recompiled my Custom UI WX Project as 32bit and it does
> launch and install 64bit binaries o
Yes, if you go with burn the desire is to not show any UI from any of the
installers. From what I understand, you have a feature tree in your MSI that
your users can change. In that case, you would need to write a BA to do the
feature tree and then pass in the options via a MsiProperty element.
Thanks Jacob, I recompiled my Custom UI WX Project as 32bit and it does
launch and install 64bit binaries on a 64bit box. I just wanted to confirm
that it was the standard practice. I guess just wanted everything on 64bit
OS to be 64bit :)
Thanks
Raj
On Fri, Jan 11, 2013 at 2:56 PM, Hoover, Jac
I'm writing the installation for a software package, and want to use the
features selection to do so, and have it mostly running okay in the .msi. The
software uses .NET, so I'd like the option to automatically install if it isn't
installed - thus, I have been led to burn.
The problem is, the o
Hmm, not certain on this but do you really need your BA to be 64 bit? Wouldn't
just the MSI/EXE installation packs need to be x64? Don't you want a single
bundle that would install your application on either an x86 or x64, using the
VersionNT64 in your conditions to decide which subset of instal
hey all
Is making a 64bit boot strapper supported by wix 3.7. I am trying to make
a 64bit custom bootstrapper and i get the following error in the
installation log
[1120:17E8][2013-01-11T14:27:10]i000: Loading managed bootstrapper
application.
[1120:17E8][2013-01-11T14:27:10]e000: Error 0x800700
What would be awesome is if the DIFxApp people would donate a copy of their
code to the WiX toolset so we could take it forward (and fix the upgrade
issues and who knows what else).
I had zero pull with them (and have even less now ) but if someone
out there has a big driver installation and can t
Not a supported scenario, never tried. If you get it working, it may break
in the future.
On Fri, Jan 11, 2013 at 6:23 AM, Raphael DUCOM wrote:
> Hi Rob,
>
> Can you confirm there is no workaround letting us to put
>
> into the BA manifest ?
>
> Waiting for your answer,
> Thanks in advance,
>
This did the trick for us:
I haven't had any complaints in a long time now since doing this. At this
point, I would always schedule things this way if using DIFxApp. As I
described in the message you quoted, we previously had
RemoveExistingProducts scheduled after InstallI
The idea is that you have a variable of type WCA_TODO that's set normally,
then overridden in an #ifdef DEBUG block to whatever the mutation is.
I am sorry.. can one of you explain this in detail?
Where should this variable be set?
Kindly explain.
I am new to all of this.. so kindly excuse my
You could move all your configuration steps and associated UI into a
stand-alone elevated .exe and add it to the bundle to be executed at the end,
or even install this configuration tool and spawn it after the installation
is complete. This would also allow you to re-configure your application
with
Hmmm.
I generally want my immediate custom actions to behave the same in install,
reinstall or upgrade. I generally block the running of immediate custom
actions in uninstall if I don't need them.
I do have several scheduling custom actions, but only four: the VsdbCmd
scheduler, the SqlPack
Hello Bob,
Thanks for assisting me with your answers.
Do you have any ideas on how i could achieve the following:
-How do you test the entries in AppSearch, RegLocator etc tables i.e the
data contained in standard tables in windows installer?
The msi built using Lux does not contain so many s
Move this line: AFTER this
line: http://schemas.microsoft.com/wix/2006/wi";>
Steve
-Original Message-
From: Rahul V [mailto:rahul8...@gmail.com]
Sent: January-11-13 5:18 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] assigning path for directory using preprocessors
Hi,
I
Hi Raphael,
I've used mt.exe in the Windows SDK to update the manifest embedded in an
application before. While I've never tried it with a BA generated by burn could
you not use it, or a similar tool, to patch the manifest of the BA *after* it
is built by Wix?
Daniel Madill
-Original Mes
The pre-requisite bootstrapper seems to only kick in if your application
fails to load, so if your MBA actually needed .NET 4.5 it would fail to
load with just .NET 4.0 installed at which point the pre-requisite
bootstrapper kicks in.
Nicholas
On 11 January 2013 13:40, Thomas Hammond wrote:
> Y
I would say that as a hack you could write a program that modifies/adds
the manifest resource. it's not so much complicated.
On 11/01/2013 15:23, Raphael DUCOM wrote:
> Hi Rob,
>
> Can you confirm there is no workaround letting us to put
>
> into the BA manifest ?
>
> Waiting for your answer,
I think you are getting attributes mixed up. The path goes in the FileSource
attribute.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 11 January 2013 14:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] assigning path for d
Hi Rob,
Can you confirm there is no workaround letting us to put
into
the BA manifest ?
Waiting for your answer,
Thanks in advance,
Bests,
Raphael DUCOM
Raphael DUCOM
Développeur
Tel : | Fax : +33 979 999 341
Web : www.prodware.fr
-Message d'origine-
De : Raphael DUCOM
Envoyé : m
Id attributes must follow the Windows Installer requirements for
identifier, which are basically the same as most programming languages.
On Fri, Jan 11, 2013 at 2:18 AM, Rahul V wrote:
> Hi,
> I am trying to assign the below path for directory by the variable
> HelpSourceFolder as shown in bel
During Modify the Engine assumes no changes to the packages is required.
The BA can then override that decision for the few packages that are
"modified".
On Thu, Jan 10, 2013 at 11:23 PM, Neil Sleightholm wrote:
> I have spent some time trying this and the modify action doesn't seem to
> do anyt
It isn't a variable it is a localisation string used in HyperlinkTheme.xml
- so effectively it is static text shown on the Success page as defined in
HyperlinkTheme.xml.
Neil
>In HyperlinkTheme.xml and HyperlinkTheme.wxl there is variable
>'SuccessHeader' which displays the success message on su
You can write a custom BA in C# although it is not something I have done.
Neil
>Thanks for the reply Neil.
>
>Can src\Setup\WixBA(C#) be used in place of src\ext\BalExtension(C++)?
>Not very comfortable to modify BalExtension(C++) so if I modify WixBA
>according to my UI need and refer in my boo
Yes, it looks like it would actually do that. However, what if my bootstrapper
application actually needed .NET 4.5? Would it install it as a prereq, or would
by bootstrapper just fail to load? Also, I am really curious why it just
doesn't behave the same way it would if .NET 4.0 isn't installed
In HyperlinkTheme.xml and HyperlinkTheme.wxl there is variable 'SuccessHeader'
which displays the success message on successful installation and
un-installation.
However I checked the whole code for wixstdba and I did not find where this
variable or control is being used or implemented. I found
Thanks for the reply Neil.
Can src\Setup\WixBA(C#) be used in place of src\ext\BalExtension(C++)?
Not very comfortable to modify BalExtension(C++) so if I modify WixBA according
to my UI need and refer in my bootstrapper application will it work?
Will the below code be the same if I replace WixB
The code for the UI is the wixstdba project, this is C++ not C #. If you
want to self contained starting point for your custom version this should
help http://wixextba.codeplex.com/.
Neil
>Currently I am referring WixBalExtension.dll in my bootstrapper project.
>I need to have my own message on
Currently I am referring WixBalExtension.dll in my bootstrapper project. I need
to have my own message on the installer window on successful installation and
successful un-installation. I tried to customize the theme files but it seems
that is not enough as there is common message being shown on
Hi,
I am trying to assign the below path for directory by the variable
HelpSourceFolder as shown in below, I am getting the error "Error 1 The
Directory/@Id attribute's value, 'D:\SomeFolder\Path', is not a legal
identifier.", please help me to identify what is wrong here.
http://schemas.micro
Does Burn not just install .NET 4.5 in your bootstrapper's main apply phase
along with everything else? If you put it first in your chain, it should
get installed first by Burn.
Nicholas
On 10 January 2013 21:19, Thomas Hammond wrote:
> I updated my bundle to use .NET 4.5 as the Mba Prereq. Th
Hi John,
I did not think it was possible after trying multiple things, I'm glad there
is a work around however. Do you have a quick sample you could show me?
Kind Regards,
Natalie Carr
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, January 10, 2013
35 matches
Mail list logo
