Fix companion file error without breaking component rules

I have an MSI which consists of a number of components. In many cases a
component consists of two files, a DLL which is the keypath and the DLL's
PDB file which has the DLL as it's companion file. I just realized that we
have a cut/paste typo, the TWO.PDB file has a companion file of ONE.DLL
(instead of TWO.DLL).

Can I fix that without breaking the component rules?

Yes, if you're doing a major upgrade. No if you're making a patch or a minor
upgrade keeping the same ProductCode guid.
--
Phil Wilson

"John Vottero" <JVottero@mvpsi.com> wrote in message
news:9C2384CE-6C3E-4933-A76D-2FE82855CA0B@microsoft.com...
>I have an MSI which consists of a number of components. In many cases a
>component consists of two files, a DLL which is the keypath and the DLL's
>PDB file which has the DLL as it's companion file. I just realized that we
>have a cut/paste typo, the TWO.PDB file has a companion file of ONE.DLL
>(instead of TWO.DLL).
>
> Can I fix that without breaking the component rules?
>