[WiX-users] Creating patch / AssemblyFileVersion

Hi, Is MSIMSP looking only at the AssemblyFileVersion of the files? I get a patch that does not patching when the AssemblyFileVersion of original and patched version are the same. Install log says for the most files that only have new AssemblyVersion: "MSI (s) (88:3C) [16:44:59:719]: The file repr

Re: [WiX-users] Failure Injection for Upgrade/Rollback Testing

On 16-May-11 18:22, Castro, Edwin G. (Hillsboro) wrote: > What would be an easy way to simulate (or cause) a failure during a major > upgrade to demonstrate the results of a rollback? See WixFailWhenDeferred in WixUtilExtension. -- sig://boB http://joyofsetup.com/ -

Re: [WiX-users] Chaining MSIs together

On 16-May-11 14:07, Kevin MacDonald wrote: > behind the times. All I know is that they have specifically requested a > single MSI. That requires the use of an embedded chainer, which requires MSI 4.5 or later. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] Failure Injection for Upgrade/Rollback Testing

A dumb little vbscript that does a divide by zero works for me - I change the condition directly in the MSI file to 1 when I want to test the failure. Phil Wilson -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Monday, May 16, 2011 3:23 PM

[WiX-users] Failure Injection for Upgrade/Rollback Testing

What would be an easy way to simulate (or cause) a failure during a major upgrade to demonstrate the results of a rollback? Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the enviro

Re: [WiX-users] Detection of run-time DLLs

There are plenty of issues here that can't be easily solved: 1. By definition you cannot detect COM dependencies because it's runtime binding. 2. They get complicated by the constantly changing OS capabilities. It's easy to say that you depend on something like the .NET 3.5 framework but then

Re: [WiX-users] Detection of run-time DLLs

What is the list of "runtime" dependencies that will be detected by the feature? More importantly what should be done in response to such a detection? Should the feature generate a launch condition to fail the installation? Should the feature generate code to automatically download and install the

Re: [WiX-users] Detection of run-time DLLs

It's hard to articulate in a short email.  Basically what I'm trying to say is when you have thousands of files that get organized into hundreds of assets and used to compose dozens of products  that you have to be very methodical in the way that you factor your dependency relationships.   Autom

Re: [WiX-users] Detection of run-time DLLs

So you would say, it's impossible with the Windows Installer XML tool set? Or is it possible but insane? Am 16.05.2011 20:14, schrieb Christopher Painter: > I maintain installers that rival Visual Studio in terms of size and > complexity. Factoring dependency relationships is critical and can

Re: [WiX-users] Detection of run-time DLLs

I maintain installers that rival  Visual Studio in terms of size and complexity.  Factoring dependency relationships is critical and cannot be automated.   I've streamlined the process to the point that it's insanely fast and easy to follow the established patterns but it still takes a human to

Re: [WiX-users] Chaining MSIs together

Many of our customers are school districts whom I suspect are somewhat behind the times. All I know is that they have specifically requested a single MSI. In my situation I need to invoke two third party executables which I assume are bootstrappers. They definitely launch MSIs internally, which is

[WiX-users] Help with updating Heat output files to be installed into GAC

Hi, I'm trying during the harvesting of files with Heat to update the resulting *.wxs file adding assembly=".net" to the files I need to install into the GAC. I came across the following link, but I can't seem to get it to work. My *.wxs file after building does not have assembly=".net" added to

[WiX-users] Conditionnal Installation of Component

Hello everyone, I'm new to WIX. Yes another OK, I have a Modular Client-Server Application to Install. I could have 3 type of installation: 1- Client 2- Server 3- Client and Server on the same computer When I install the Client and the Client Server (Client part are common

Re: [WiX-users] Detection of run-time DLLs

Am 16.05.2011 17:53, schrieb Christopher Painter: > To be honest, that's not a "feature" of InstallShield that I like or use. > Magically "Easy" buttons are a great concept but I don't like switching off > my brain. > Yea, maybe. But it's not necessary to switch off any brain, when such a dep

Re: [WiX-users] Detection of run-time DLLs

To be honest, that's not a "feature" of InstallShield that I like or use.  Magically "Easy" buttons are a great concept but I don't like switching off my brain. --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserve

[WiX-users] Detection of run-time DLLs

Hello, I know from InstallShield (IS) that it is capable to detect all the dependencies of a binary to run-time DLLs. When VS2005 C++ DLL uses the msvcrt IS adds the corresponding MSM to the project. How can do similar with WiX 3.5? It would includ this tasks: - detect automagically which run

[WiX-users] Windows Installer Query Tool - built on WIX DTF, feedback needed

Hello, I want to announce tool that would be useful for Windows Installer XML DTF and MSI package design cases. It allows to experiment with MS SQL queries and provides output in Microsoft Excel sheet. Also there is ability to filter outputs based on different criteria, including regular expressio

Re: [WiX-users] Integrity of WiX binaries

To the OP, why doesn't your organization just download the source and build the binaries themselves? That will solve the "integrity validation of all software used in the build process" requirement. They can even sign the exes with their own certs. Open source FTW :) -Original Message- Fr