Do you not know the name of your EXE at compile time? You could hard code
the name of the executable, or you could use the preprocessor.
$(var.ProjectName.TargetFileName) will get you the file name of the output
of the project with name 'ProjectName' if you've set up the references in
Visual Stud
If you want just the file name, I think you'd need to write a custom action
to get that. Why are you interested in just the file name of a particular
file?
Nicholas
On 27 October 2014 13:32, soldag wrote:
> Hello,
>
> I am currently working on an installer for my software using the WiX
> tools
Hi,
I think you'll want to add a VerifyPath attribute to the XmlConfig element
that creates the 'add' element so that it doesn't pick up the existing
element called 'add'. It will need to be something like
"//configuration/location/system.webServer/modules/add[[]@name='Blah,
Blah.2.2013'[]]", whi
You can use Burn to chain together 3rd party pre-requisites and your
MSI(s). Detecting hotfixes is the tricky part. I believe the cannonical
way to do so is via WMI, which you can do if you write your own
bootstrapper application (BA) for Burn, but if you only want to use what
comes out of the bo
Just write the version number, with a v in front and no quoting
(i.e. SQL_SERVER_VERSION >= v10.50).
Nicholas
On 27 June 2013 16:06, snowkoan wrote:
> Cool. So we have a Burn variable called SqlCe40Version, that contains a
> version string like "14.0.0.0"
>
> How can we do a version comparison
get tracked.
>
>
> On Thu, Jun 6, 2013 at 3:01 AM, Nicholas Pierce <
> nicholas.pie...@permasense.com> wrote:
>
> > I think that exit code from SQL Server means that the RebootRequiredCheck
> > rule failed, so something further up the chain or something that was
> >
I think that exit code from SQL Server means that the RebootRequiredCheck
rule failed, so something further up the chain or something that was
installed previously is wanting a reboot. You can disable the reboot
required check with the /skiprules=RebootRequiredCheck parameter, or you
can force Bur
You would need to write your own ExePackage that ran the EXE that did the
relevant calling and waited around for child processes. If an error does
occur, you'll need to return a non-zero exit code as that's how Burn
determines whether a package succeeded or not.
If the exe you're currently callin
code looks like this:
>
>
> public RelayCommand LicenseTermsCommand
> {
> get
> {
> if (licenseTermsCommand == null)
> {
> licenseTermsCommand = new RelayCommand(() =>
> Process.Start("EULA
If it's a payload in your BootstrapperApplicationRef, then it'll be
extracted to the same directory as the burn engine and your Managed BA
assembly, so you should be able to get the path from that.
Nicholas
On 4 June 2013 17:34, Carlos Hdz Taylor wrote:
> Hello guys,
>
>
> I am new to WiX, I ju
If you want some more logic to the installation of pre-requisites, I think
you'll need to make another Burn Bundle to act as your pre-requisite.
That's what we had to go to get .net 4 and Windows Imaging Component to
install as a prerequisite on Server 2003. This will just be a super simple
bundl
if .NET 4.0 isn't
> installed. The detect condition is false, so it seems like there is
> something strange going on in there.
>
> -Thom
>
> -----Original Message-
> From: Nicholas Pierce [mailto:nicholas.pie...@permasense.com]
> Sent: Friday, January 11, 2013 4:31 AM
>
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
>
> Steve
>
> -Original Message-
> From: Nicholas Pierce [mailto:nicholas.pie...@permasense.com]
> Sent: January-07-13 11:44 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] custom action to run SQL Server Express EXE
>
&g
Why not just use Burn to run the SQL Server installers?
Nicholas
On 7 January 2013 16:31, Steven Ogilvie wrote:
> Hi,
>
> In my Database dialog I am allowing the user to choose whether to use
> their own copy of SQL Server or use a dedicated SQL Server Express 2012.
>
> If they choose the dedic
You can use the InstallCondition attribute of MsiPackage (or ExePackage or
MsuPackage) to control whether a package is installed. If InstallCondition
evaluates to true, then the package is installed, but if InstallCondition
evaluates to false, then the package will be removed unless it's permanent
Hi,
I have written a ManagedBootstrapperApplication that requires .net 4.0.
On Windows 2003 and XP, this requires the Windows Imaging Component, so
I've used another Burn bootstrapper to install the appropriate
prerequisites as per this post:
http://windows-installer-xml-wix-toolset.687559.n2.nab
Hi,
We're starting to use Burn in our software deployment, which includes SQL
Server 2008 R2, which requires Windows Installer 4.5, which on Windows
Server 2008 and Windows Vista requires an MSU package to be installed. In
my WiX source files I have:
...
...
...
These get picked up correctly
18 matches
Mail list logo
