oing is very unusual. Since it's
> so unusual, you should manage the GUID manually. It certainly isn't a design
> we'd generally encourage.
>
> ___________
> FireGiant | Dedicated support for the WiX toolset |
I recently filed bug 4448, in which the following response was posted:
Versioned companion files are atypical and would seem to bring their
own problems for upgrades and patching. We don't plan to expand *
GUIDs to cover this case.
That bug is probably not the right place to ask this,
On 29-05-2014 19:13, Phil Wilson wrote:
> Yes, in this case scheduling RemoveExistingProducts before
> CostInitialize should solve the problem if it's related to this:
Yeah, that is what I figured. Unfortunately, that is not a legal
scheduling. According to
http://msdn.microsoft.com/en-us/library
We have a product that ships with a number of independently versioned
third-party libraries, in addition to our own files (whose file versions
follow the product version)
Now, we've encountered a situation where some of the third party files
we want to ship in our installer have a lower version
4 matches
Mail list logo
