I was searching around for a solution to easily update my MSI version
numbers with each build, but I couldn't find one. So I wrote this and now I
don't have to remember. Thought I'd share...
A C# 3.5 console app:
using System;
using System.IO;
static class VersionUpdater
{
///
///
I know we can configure a Launch Condition to check for the existence of
another installed product before installing, but is there a way to enforce
or at least warn the user if they later attempt to uninstall the
prerequisite (especially if we author the prerequisite)?
I guess there could be a lau
Ok, thanks for the links. I'm going to be working through them, but at
first glance, I can tell I still need a hint.
I can't tell if you're suggesting that if I understood Component Rules, I'd
know that what I'm looking to do violates those rules. Is that what you're
saying?
More generally, is
Hi Bob,
I guess I'm completely missing how to version files then. I don't find any
attributes or child elements of component or file that seem related. I'm
not aware of any consistent file-versioning aspect of the windows file
systems. Also, I expect a need to version non-files, such as registr
Can someone please detail how Merge Module versioning is supposed to work?
I cannot find guidance anywhere for Merge Module versioning (especially in
WiX). I've seen WiXLibraries, so if that would work better, please tell me
how.
The scenario, which I believe is common: Certain shared files and
This has to be a common need yet I find hardly ANY references to it on the
web...
I've got a product that has three sets of components, one installed on the
server, one on the web head, and one on the developer's machine. All three
sets could be installed on one machine and should peacefully coexi
6 matches
Mail list logo
