I have 3 version of my product, v1/v2/v3.

v1 and v2 have been released. v2 included a v1->v2 patch.

After release we found a bug in the v2 patch that makes the system unstable
and would cause a v2->v3 patch to fail.

v1 original install is able to patch to v3, and a v2 original install can
patch to v3.

My question is, can a custom action in my v3 patch detect whether the v2
installation it is updating was an original installation or a result of the
buggy v2 patch?

"EP" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
> I have 3 version of my product, v1/v2/v3.
>
> v1 and v2 have been released. v2 included a v1->v2 patch.
>
> After release we found a bug in the v2 patch that makes the system unstable
> and would cause a v2->v3 patch to fail.
>
> v1 original install is able to patch to v3, and a v2 original install can
> patch to v3.
>
> My question is, can a custom action in my v3 patch detect whether the v2
> installation it is updating was an original installation or a result of the
> buggy v2 patch?

If the bug is in the form of an incorrect file, maybe you could try
searching for that file using the AppSearch / Signature tables?

If not, maybe the ListOfPatchGUIDsToReplace property in the PCP file
would help you?

/ Jorma

If you updated the ProductVersion each time, from something like 1.0.0.0 to
1.0.0.1, 1.0.0.2 etc, you could get the ProductVersion of the installed
product.
--
Phil Wilson [MVP Windows Installer]
----
"EP" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> I have 3 version of my product, v1/v2/v3.
>
> v1 and v2 have been released. v2 included a v1->v2 patch.
>
> After release we found a bug in the v2 patch that makes the system
unstable
> and would cause a v2->v3 patch to fail.
>
> v1 original install is able to patch to v3, and a v2 original install can
> patch to v3.
>
> My question is, can a custom action in my v3 patch detect whether the v2
> installation it is updating was an original installation or a result of
the
> buggy v2 patch?
>
>