cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
conorhoran
Level 4

Setting System.AppUserModel.ID during install

Jump to solution

Hi,

I have a request to provide the AMUID (System.AppUserModel.ID) for two executable components we install during a product install.

In previous iterations of the installer package we placed a shortcut to a VBScript start-up script which calls the applications for us on start-up. The applications being called exist on the disk but are not present in the shell:AppsFolder (virtual application directory).

We are now running this software in kiosk mode and this requires that we provide AMUID to the kiosk so it can call the two executables directly (without script).

To do this, we are attempting to add a shortcut to the executable component so we can specify the AMUID in the MSIShortcutProperty table.

Is there any documentation on how exactly we can achieve this? We basically want the app to appear in the "Applications" virtual folder so it will show it's AMUID when we query it with Powershell command "get-startapps".

Note, the project is currently built using the Installshield Premier 2013 IDE, we have a license for Premier 2018 and Professional 2018 but the project has not been upgraded yet.

References below:

MSIShortcutProperty

https://docs.microsoft.com/en-gb/windows/win32/msi/msishortcutproperty-table?redirectedfrom=MSDN

System.AppUserModel.ID

https://docs.microsoft.com/en-us/windows/win32/properties/props-system-appusermodel-id

Application User Model IDs

https://docs.microsoft.com/en-gb/windows/win32/shell/appids?redirectedfrom=MSDN

Thanks in advance.

Regards,

Conor

 

Labels (1)
0 Kudos
(1) Solution
banna_k
Revenera
Revenera

Hi @conorhoran,

Can you check this can be configured through the "Shell  Properties" setting available in the shortcut. 

In shortcut view, create a shortcut for your application and then go to the "Shell Properties" settings. There is an option to configure custom property if it is not under the predefined properties.

More information can be found at the below link:

https://docs.flexera.com/installshield25helplib/helplibrary/SettingShellShtctProp.htm

https://docs.flexera.com/installshield23helplib/helplibrary/IHelpMarsShortcutProperties.htm#ref-views_3738735522_1161257

Shell Properties

Basic MSI, DIM, InstallScript MSI, Merge Module, MSI Database, MSM Database, Transform

This setting lets you specify one or more shortcut properties that need to be set by the Windows Shell at run time.

To specify one or more properties, click the Add New Shell Shortcut Property button in this setting, and then click one of the available options:

  Prevent Pinning—The context menu commands for pinning the shortcut to the taskbar or the Start menu are not displayed for this shortcut after end users install your product. In addition, this option makes the target of the shortcut ineligible for inclusion in the most frequently used list on the Start menu.

If you select this option, InstallShield adds a Key Name setting, plus additional rows of subsettings, and configures them as needed.

  Do Not Highlight as New—The Start menu entry for the shortcut is not highlighted as newly installed after end users install your product. This has the same effect as clearing the Highlight newly installed programs check box in the Customize Start Menu dialog box for an individual item on a target system. You may want to set this property for shortcuts that are for tools and secondary products that are part of your installation. If you select this option, InstallShield adds a Key Name setting, plus additional rows of subsettings, and configures them as needed.
  Suppress Initial Pin to Windows 8 Start Screen—If you select this option, InstallShield suppresses the Windows 8 default behavior of pinning a shortcut to the Start screen during initial installation on Windows 8 target systems. The installation sets a Windows Shell property that was introduced in Windows 8. You may want to suppress pinning for shortcuts that are tools and secondary products that are part of your installation.
  Custom Property—To specify a custom property and value for shortcut properties that need to be set by the Windows Shell at installation run time, select this option. InstallShield adds a new Key Name setting, plus additional subsettings, that let you configure the appropriate property name and value.

Specify additional properties as needed.

Note • Windows Installer 5 introduced support for the Shell property settings. Earlier versions of Windows Installer ignore these settings.

For more information, see Setting Shell Properties for a Shortcut.

 

 

View solution in original post

0 Kudos
(2) Replies
banna_k
Revenera
Revenera

Hi @conorhoran,

Can you check this can be configured through the "Shell  Properties" setting available in the shortcut. 

In shortcut view, create a shortcut for your application and then go to the "Shell Properties" settings. There is an option to configure custom property if it is not under the predefined properties.

More information can be found at the below link:

https://docs.flexera.com/installshield25helplib/helplibrary/SettingShellShtctProp.htm

https://docs.flexera.com/installshield23helplib/helplibrary/IHelpMarsShortcutProperties.htm#ref-views_3738735522_1161257

Shell Properties

Basic MSI, DIM, InstallScript MSI, Merge Module, MSI Database, MSM Database, Transform

This setting lets you specify one or more shortcut properties that need to be set by the Windows Shell at run time.

To specify one or more properties, click the Add New Shell Shortcut Property button in this setting, and then click one of the available options:

  Prevent Pinning—The context menu commands for pinning the shortcut to the taskbar or the Start menu are not displayed for this shortcut after end users install your product. In addition, this option makes the target of the shortcut ineligible for inclusion in the most frequently used list on the Start menu.

If you select this option, InstallShield adds a Key Name setting, plus additional rows of subsettings, and configures them as needed.

  Do Not Highlight as New—The Start menu entry for the shortcut is not highlighted as newly installed after end users install your product. This has the same effect as clearing the Highlight newly installed programs check box in the Customize Start Menu dialog box for an individual item on a target system. You may want to set this property for shortcuts that are for tools and secondary products that are part of your installation. If you select this option, InstallShield adds a Key Name setting, plus additional rows of subsettings, and configures them as needed.
  Suppress Initial Pin to Windows 8 Start Screen—If you select this option, InstallShield suppresses the Windows 8 default behavior of pinning a shortcut to the Start screen during initial installation on Windows 8 target systems. The installation sets a Windows Shell property that was introduced in Windows 8. You may want to suppress pinning for shortcuts that are tools and secondary products that are part of your installation.
  Custom Property—To specify a custom property and value for shortcut properties that need to be set by the Windows Shell at installation run time, select this option. InstallShield adds a new Key Name setting, plus additional subsettings, that let you configure the appropriate property name and value.

Specify additional properties as needed.

Note • Windows Installer 5 introduced support for the Shell property settings. Earlier versions of Windows Installer ignore these settings.

For more information, see Setting Shell Properties for a Shortcut.

 

 

0 Kudos
Hi @banna_k,

Thanks for reply.

Creating a shortcut to our executables in the Programs folder allowed us to get the AMUID.

We did not need to specify any explicit settings for this. Previously we were only installing executables directly into INSTALLDIR under the Program Files root.

Having a shortcut in programs allows the app to show in Windows Search and provide AMUID when queried.

Thanks for help.

Regards,
Conor
0 Kudos