Hello,
I’m pretty new into using the WIX toolset and I have written an custom MBA for
the installation of our software products using Wix Toolset 3.9.901
Here is a part of the bundle.wxs file that is used:
WixVariable Id=WixMbaPrereqPackageId Value=NetFx452Redist /
WixVariable
That is not currently supported. That may be supported in Wix 3.9 depending on
how the RTM looks.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
I was installing an update to one of our (virtual) machines and noticed that it
failed, complaining that an installation was in progress. Since sometimes SCCM
and other things auto-drop for us, I figured I'd look to see what it was. With
procexp, I found an msiexec -Embedding call being run.
Not a wix question, but a quick google search shows it's related to custom
actions. http://blogs.msdn.com/b/astebner/archive/2005/03/02/384088.aspx
-Original Message-
From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca]
Sent: Thursday, October 02, 2014 9:47 AM
To:
Hallo Andreas,
it looks like you have the right pieces, but there are some differences
from how my bundle typically looks:
- I hope it's a typo that your prereq is NetFx452Redist but further down in
the PackageGroupRef you're referencing NetFx451Redist? That second one
should probably be
Hey guys,
Just ramping up to upgrade from 3.7 to 3.9 and it appears as though I can only
have 1 version installed (via the installer) at a time on my development box.
This has me a touch concerned.
I would really like to maintain older versions of our product with the version
of WiX that
You don't need WiX installed to use it. Check out the Integrating WiX Projects
Into Daily Builds topic in the help file.
Short version is to download the binaries zip, put it in a known location on
your build machine, and then use
PropertyGroup
How does that translate into usage by developers? Where is [[Version]] pulled
from?
I see the following at the top of my wixproj files
Project ToolsVersion=4.0 DefaultTargets=Build
xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
Import Project=../../WiXVersioning.targets /
Jacob is correct. To answer your questions:
1. Why exclusive? No one has put forth the (large?) effort to make the MSBuild
and Visual Studio integration work side-by-side. Do what Jacob says for SxS.
2. SDK folder? We're trying to get those in sync but they would be breaking
changes in WiX
Hi,
I have used conditional component install this way, which works for me when I
don't want to install a file in some situations:
Component Id=someComponent Guid={DE943477-4229-45f8-8A02-5300ACCC6A39}
ConditionKEY_FOUND/Condition
File Id=someFIle Source=\file_path KeyPath=yes
2 is the approach I've been involved with, but the feature that makes
it more corporate friendly is to allow it to be silent and read a file
with all the parameters that would have been entered using the UI
wizard.
The general approach is that each relevant data item on a form has a
public
Hello, Yes You have to add SKU in bootstrapper.config
like this
startup useLegacyV2RuntimeActivationPolicy=true
supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.5 /
/startup
as stated here http://stackoverflow.com/a/18227544/150
I remember I had the same problem.
I have an XML file driven approach where in it reads the XML file, sets the
appropriate properties, and continues the install without further UI.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® |
That is correct. Information that needs to persist to a repair or upgrade is
persisted in the registry.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Hi guys,
That sounds great and I've considered these approaches before. However, as I
understand it (and I may well be wrong), when a repair or modify is invoked
through the Programs and Features application (appwiz.cpl), it's not going to
be able to see the original configuration file so all
I would only gather the minimum required information needed to install the
application. Utilize a configure on first run model for application
configuration, and write to an application/user defined storage location so
that the user data is automatically persisted on repair/modify.
Newer
On 02-Oct-14 03:25, Orzyszek Andreas wrote:
The problem i’m faceing is that if I run the setup on a machine with .Net 4.0
Full installed the .Net 4.5.2 is not installed before my custom MBA is
started.
That's by design. If your BA can be loaded, it is.
--
sig://boB
http://joyofsetup.com/
On 27-Sep-14 16:33, Nick Ramirez wrote:
RemoveOnUninstall=no
...
When I run this installer, the existing user is updated so that it is now a
member of the Administrators group. However, on uninstall, the membership is
not removed from that user. Is there something else I need to add to make
On 01-Oct-14 18:43, Colin Sim wrote:
I have some questions about how best to deal with install or setup
configuration data.
Install defaults in per-machine locations (e.g., HKLM or ProgramData).
The first time the app runs, copy it to the running user's per-user
locations (HKCU/AppData).
--
And in the case of AD deployment, you'll just roll out a configuration file
along with the MSI install?
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Friday, 3 October 2014 11:00 a.m.
To: General discussion about the WiX toolset.
Subject: Re:
It depends. We don't access AD directly. We call ADFS through a wrapper
service. Since many of our services have hundreds of users, roles, etc., UI
entry is prohibitive. We load a database instead. Not as flexible, but plenty
fast.
--
John Merryweather Cooper
Senior Software Engineer |
Use Group Policy.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Colin Sim [mailto:colin@ipfx.com]
Sent: Thursday, October 2, 2014 3:20 PM
To: General discussion
22 matches
Mail list logo
