I hoped that i didn't have to use a custom BA for things like that, because
like preventing the install of SP1FP1 without SP1 installed seemed to be
such a fundamental concept.
On Mon, Jun 17, 2013 at 11:08 PM, Blair Murri wrote:
> would work? A custom BA can always do whatever it wants
> in t
Hello,
I am trying to include the MS SQL CE 3.5 SP2 as part of my setup prerequisites.
However, this part rolls back after it completes. I turned on the
DisplayInternalUI to see the last dialog box of the installation. After that,
MSSQL CE got uninstalled and I got two install log files in the
Look at it this way. Visual Studio 2012 Ultimate shows as one ARP entry but in
reality it installed several "hidden" MSI's (I forget if it was 119 or ...).
Since the system as a whole is needed for the application to function, you
wouldn't want hundreds of packages visible in ARP if they shoul
I built my bundle, and ran it, which installed everything in the chain.
Then I rebuilt my bundle, and ran it, without incrementing Version,
which installed nothing, except it did add itself to "Programs and
Features". I now see two entries for the same Version of the installer:
one that actually i
Writing documentation required a depth of knowledge which I don't presently
have. The WiX documentation suffers from presuming the user already has a
deep understanding.
Take a look at "Fundamental Tools and Concepts". There's NOTHING there!
No concepts at all! It's nothing more than a list of
That zip file appears to contain a solution with sources from two projects but
I didn't see the build log that presumably this error is reported in.
> From: jocoo...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 17 Jun 2013 17:22:46 +
> Subject: Re: [WiX-users] Catastrophi
would work? A custom BA can always do whatever it wants in
this area.
Blair
> From: subscr...@gmail.com
> Date: Mon, 17 Jun 2013 11:54:54 +0200
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] prevent installation of bundle a bundle specific version
> is not installed
>
> Hi all
If you wanted to use the literal ™ for TM you would need to set your XML
to codepage 1252 in the directive at the top of the file. By default
XML uses UTF-8 unless you are explicit (or a BOM or other obvious means such as
UCS-2/UTF-16 or UCS-4 encoding was used on the WXS/WXL/WXI file).
> Fro
George,
On initial installations Windows Installer seems to be a little more lenient in
passing public properties that are not secure while being more stringent in
maintenance operations (such as repairs). There are rules (search MSDN for
secure properties in the windows installer section) but
If you'd like to help us improve the documentation, that would be great.
Unfortunately, we don't always think of every use case possible. The WiX
toolset is extremely powerful so the space to document is pretty large.
On Mon, Jun 17, 2013 at 12:55 PM, Tad Carlucci wrote:
> Actually, I was able t
Actually, I was able to do a web search and find a Very Old example of how
to handle upgrades which actually described what why each XML clause was
needed, and what it did. To bad the so-called documentation doesn't do
that!
I'll show what I came up with for the Basic case, so far.
1. If a Bundle fails to install everything in the chain, it should rollback
and not have anything left in ARP.
2. If you want it to block, your BA would need to do that. If you're using
wixstdba, I think it automatically blocks downgrades. IIRC, it doesn't
block same versions because that's not a
If you always increment the version, the new bundle will always remove the old
bundle, and you won't get duplicates. A simple MSBuild task to increment a
counter from a file in version control, or a method witch encodes Date/Time
into the version number will reduce or eliminate the possibility
Does anyone have a way to extract embedded transforms from the _storages table
in MSI?
I know you can do it with Msidb.exe, and I have read you can do it through OLE
structured storage APIs but have not found any examples on this method as of
yet.
Any pointers in the right direction would be
I don't understand.
If a bundle fails to install everything in the chain, why does it add it
self to "Programs and Features"?
If I already have Version 1.0.0 of a bundle installed, why would it add
another entry for Version 1.0.0?
Is there some way to use WixBundleInstalle to reject the install
In a corporate environment, this would be handled via group policy/AD or tools
like SCCM/LanDesk. As for the actual packaging, MSI's are preferred but the
tools can handle other technologies.
-Original Message-
From: Greg Edwards [mailto:gedwa...@polariswireless.com]
Sent: Monday, June
The general expectation is that when you make a new build, you'll increment
the version. The WiX toolset's Bundle increments based on the date (we
don't do multiple builds in the same day).
You could write a custom BA to allow "same version upgrades". Burn engine
doesn't have support for that yet
This is generic question to all WIX users.
I am looking for a generic deployment tool that will allow both IIS Web
Services and Windows Services to be deployed across multiple machines.
Is there such a tool? If so, what do you recommend?
Thank you.
-Greg Edwards
Use XmlFile and/or XmlConfig from the Util Extensions.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: chintala srinivas
Hi,
I am converting my projects from IS to WIX. When I dark the '.msi' the XML
File Changes data was converted into and it was not
working as expected. And when I see the msi from ORCA the ISXML File table
also not coming .
Can anyone please let me know how to add XML File Changes to wix in a
si
Incrementing Version for every single bundle is going to be problematic.
Everyone will have to track and increment this Version or suffer
duplicate entries in "Programs and Features".
If I build and install my bundle (with version=1.0.0), then build and
install my bundle again (with version=1.0.0)
The attachment WixError.txt is really a ZIP file based on the header. Comes
through as garbage although it may be recoverable.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
I've got a SQL CE 3.5 package, that's working well. It uses MSI files,
so detect is easy.
Note: There's an issue with the x86 on x64 machines:
(http://support.microsoft.com/kb/974247)
The links are for german culture installers.
Am 17.06.2013 16:03, schrieb Rob Mensching:
If you get it work
You can use Bundle/Condition for that (happens after OnDetectComplete for
WixStdBA, so you can use the results of Searches in variables). I believe the
Bundle/@Condition is intended to be evaluated before your BA is loaded, to
check for conditions where your BA won't run.
-Original Message
The "easy" answer is to install one instance of the application, and have on
first run the user enter an activation code. This code would then enable all
the functionality available for that specific code.
-Original Message-
From: Tad Carlucci [mailto:tad.carlu...@gmail.com]
Sent: Mo
The BA is provided paths to all of the log files. You could copy the log
files (or zip them up for the customer!) in a custom BA.
On Mon, Jun 17, 2013 at 6:53 AM, Adkins, Christopher <
christopher.adk...@docuware.com> wrote:
> This I was aware of, but what I was trying to do was have it so that
This I was aware of, but what I was trying to do was have it so that when the
customer double clicks on bundle.exe then all the logs from the installation
would show up in %localappdata%\temp\bundle20130617\
Asking all of our customers to explicitly install our product from the command
line so
If you get it working well, it'd be great if you could help us expand the
provided packages and we can get that code in to maybe the SqlExtension.
On Mon, Jun 17, 2013 at 6:47 AM, Michael Stoll wrote:
> I might have been unclear, sorry.
>
> I don't want to create the msi package, I just want to
I might have been unclear, sorry.
I don't want to create the msi package, I just want to bootstrap it.
If there's no msi installer, I'd stick to the exe installer.
The exe package should look somewhat like this (not testet yet)
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schema
Yes, there are three different upgrade guids already. At this point I have
it so I can install all three versions and they'll upgrade themselves and
prevent downgrades. I need to keep it to only-install-one-of-the-three and
would greatly prefer to avoid the support issues which would arise after
Hi
Run the bundle.exe like this from a command line:
$ bundle.exe /log your_logfile_location.log
The msi log files will be placed next to it.
When the bundle is executed without this parameter, you can find the log
files in
%localappdata%\temp
Cheers
Jakob
On Mon, Jun 17, 2013 at 2:13 PM, Adki
Hi everyone,
I am sure that I am missing something, but I can't seem to figure out how to
configure where the installation logs land. The installation that I am putting
together is going to contain 30+ MSIs and the support technicians that I work
with have requested that all the logs are in one
Hi all
When we provide patch bundles for deployed service packs, the fixpacks only
contain the difference to the bundle ServicePack1.
Currently, the SP1 FixPack1 bundle installs also on systems where SP1 doesn
not exist, leading to the msp patch not being installed (SP1 missing), but
the bundle be
Scratch that - there is already bug on this:
http://sourceforge.net/p/wix/bugs/3109/
-Original Message-
From: Philip Patrick [mailto:patri...@varonis.com]
Sent: Sunday, June 16, 2013 18:31
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper reboots automatically
Hi,
I would start trying to use 3 different upgrade codes and using Upgrade table
to prevent installation of "lower" versions of the product. My concert in this
approach - not sure if upgrade from Lite to Basic to Premium will work smoothly
- just need to find it out empirically.
If it won't work -
35 matches
Mail list logo
