Override Windows Installer... --> Custom Name [missing]

[Zardoz2293]

Product Information -->
Product Details -->
Add or Remove Programs (Control Panel) -->
Override Windows Installer programs list entry -->
Custom Name: -->
Enter any custom name that includes brackets such as: "[Test] Example - [|ProductName]"

Now, (right-click) select "Resolved Value" from the pop-up menu results in "[Tool] Example - Event Manager" (CORRECT)

Build and install, review Add or Remove Programs --> " Example - Event Manager" is displayed (INCORRECT)

[GabrielBarbu]

Hello,

Bracket-enclosed strings are interpreted as pseudo-formatted properties during build time. Since there's no pseudo-formatted called 'Test', it is discarded.
Create a new property on the Install Parameters page, and input your value there: "[Test] Example - [|ProductName]" . Use that pseudo-formatted property in the Custom Name field.

Best regards,
Gabriel

[Zardoz2293]

Gabriel,

Bracket-enclosed strings are interpreted as pseudo-formatted properties during build time. Since there's no pseudo-formatted called 'Test', it is discarded.
Create a new property on the Install Parameters page, and input your value there: "[Test] Example - [|ProductName]" . Use that pseudo-formatted property in the Custom Name field.

Performed using the new property and solved. However, if you don't have a property defined (such as "[Test]"), then shouldn't the "Resolved Value" display an empty value rather than the literal value when in brackets?

[Bogdan]

Hi,

then shouldn't the "Resolved Value" display an empty value rather than the literal value when in brackets?

This is the normal Windows Installer behavior which Advanced Installer reproduces using its API.

If the field contains a public property which is empty Windows Installer resolves it to its name, if the field contains a
pseudoformatted value then it is resolved to an empty string.

Regards,
Bogdan

[Zardoz2293]

Relative to the original posting: Are you stating that if you display the "Resolved Value" you cannot expect to see what the Windows Installer behavior will be? If this is the case why provide a "Resolved Value" anyway, and if the "Resolved Value" doesn't match the "normal Windows Installer behavior" what value is it? You have to build the install and review only finding that the "Resolved Value" and the "normal Windows Installer behavior" are different and then continue to cycle through changes and builds until resolved? [Note: Keep in mind that in the original posting, I was not using a pseudoformatted value, and if by definition using brackets is a pseudoformatted value, then "[Test]" was an empty value that was being displayed as "[Test]" in the "Resolved Value" but "" in the WI-API].

[Bogdan]

Hi,

Are you stating that if you display the "Resolved Value" you cannot expect to see what the Windows Installer behavior will be?

Usually the resolved value in Advanced Installer matches the one shown during the actual installation. However, since it's using a property, changes made for it during install cannot be shown in Advanced Installer. For example, if the property is set by a custom action, Advanced Installer cannot run that custom action to show the final value.

If this is the case why provide a "Resolved Value" anyway

Please note that this value is an approximation for the property. It's impossible to replicate the actual behavior shown during installation. Also, most properties are resolved correctly by this option.

You have to build the install and review only finding that the "Resolved Value" and the "normal Windows Installer behavior" are different and then continue to cycle through changes and builds until resolved?

I was not using a pseudoformatted value, and if by definition using brackets is a pseudoformatted value, then "[Test]" was an empty value that was being displayed as "[Test]" in the "Resolved Value" but "" in the WI-API

This happened because you are using a private property. During install, a private property doesn't pass it's value to InstallExecuteSequence, so it may become an empty string. Try using a public property and let me know if the problem persists.

Regards,
Bogdan