David Ruddock wrote:
> 1) I wonder if anyone can shed any light on the above issue (is it
> simply an issue with VS2005 - for which there is no WiX workaround)
I can't explain why that happens -- but the general fix is to have a
"version moat" where you break backward compatibility and don't sup
Hi Bob - thanks for that help.
I reverted back to using the same Visual Studio MSM for the WiX installers
for this shared COM component (hoping that it would help). Unfortunately it
seems that this behaviour (un-installing the VS MSI breaking the COM
registration of the shared COM component used b
[EMAIL PROTECTED] wrote:
> One issue I haven't quite worked out is about migrating shared merge
> modules to wix. I've been using the same component guids as the previous
> VS2005 used (i.e. so that the componentIds match), but the shared COM
> components are now registered differently (using the r
Hi wix-users,
I've been looking into migrating as set of Visual Studio MSIs and MSMs
to WiX (v2). On the whole things are are going swimmingly!
One issue I haven't quite worked out is about migrating shared merge
modules to wix. I've been using the same component guids as the previous
VS2005 used
4 matches
Mail list logo