Talk:Microsoft Installer MSI HasRelatedProduct Macro

Why are you calling it relative when the api calls it related? You should also prefix the name of the macro with MSI since this is a MSI specific thing... --Anders 18:15, 20 April 2011 (UTC)

I was torn on just how to name this function. I choose "Relative" as the related package is a relative to it. Just as my sister is my relative as we are related.

Its all semantics really. If it makes more sense to change the name to use the term "related" instead of "relative". I can accept the reason to change it.

As for adding an "MSI" token to the name, I was also debating this as my previous development version of this macro had "MSI" in the name. I guess I was trying too hard to reduce the number of characters I have to type when I call the macro.

What sounds better to you?

• MSIRelatedPackageInstalled
• MSIPackageRelativeInstalled
• MSIPKGRelativeInstalled
• MSIRelatedPKGInstalled
• MSIRelatedInstalled
• MSIRelativeInstalled
• MSIHasRelatedInstalled
• MSIHasRelativeInstalled

--Zinthose 18:35, 20 April 2011 (UTC)

I don't know the MSI terminology well enough to know the difference between a product and a package. All I have to go on is the API used and based on that I would call it MSIHasRelatedProduct or MSI_HasRelatedProduct.

--Anders 21:22, 20 April 2011 (UTC)

---

Named Chanegd / Page Moved

MSI_HasRelatedProduct is is ^_^ --Zinthose 21:55, 20 April 2011 (UTC)