Sehremis
Posts: 12
Joined: Mon Nov 20, 2017 3:28 pm

Renaming Custom Actions

Hello everyone,

I have an Advanced Installer project that uses a number of custom actions, such as "Run PowerShell Script File" and "Launch File" (to launch bat files).

I would like to rename those steps since they're currently all called "LaunchFile", "LaunchFile_1", "LaunchFile_2" etc.

However, while the context menu offers a "Rename" option, and allows me to type in a new name, that new name is not applied, and after I press Enter, the file name goes back to "LaunchFile"

This is going to make the project rather confusing, and it feel like a bug.

Is there anything I can do about this? I am using Advanced Installer version 14.5.1 under a Professional licence on Windows Server 2016.

Thanks in advance,
Kira Resari
Sorin
Posts: 663
Joined: Mon May 08, 2017 1:03 pm

Re: Renaming Custom Actions

Hello Kira,

We couldn't reproduce this issue on our side. You should be able to rename the custom actions with the method you've mentioned. Could you please send us the .AIP (project) to support at advancedinstaller dot com so we can investigate it?

Also a testcase of how to reproduce this in a new sample project would be very helpful.

Best regards,
Sorin
Sorin Stefan - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Sehremis
Posts: 12
Joined: Mon Nov 20, 2017 3:28 pm

Re: Renaming Custom Actions

Hi Sorin,

I was able the reproduce and resolve the issue.

Apparently, the custom actions can't have names with spaces in them. Using names without spaces worked for me.

However, there is one exception:
I was not able to name a custom action "InstallServices". I guess that is because that name is already used internally at some point.

To make this more user-friendly I'd suggest making an informative pop-up bubble saying "Spaces are not allowed in custom action names." or "This name is already being used internally by Advanced Installer."

Cheers,
Kira Resar
=^,^=
Sorin
Posts: 663
Joined: Mon May 08, 2017 1:03 pm

Re: Renaming Custom Actions

Hello,

This is correct, we don't support black spaces in the custom actions names.

Regarding the InstallServices, this is a standard Windows Installer action : InstallServices Action so that's why you can't name your custom action in this way.
To make this more user-friendly I'd suggest making an informative pop-up bubble saying "Spaces are not allowed in custom action names." or "This name is already being used internally by Advanced Installer."
Thank you for your suggestion. I have added this improvement on our TODO list and maybe it will be available in a future version of Advanced Installer.

Best regards,
Sorin
Sorin Stefan - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”