Version 6: User Actions imported from 5.7 not working in existing .bld scripts

[u-winkelmann]

I just installed Visual Build Pro 6 to check if its compatible with the 5.7 Version we're currently using. However it seems that the user actions are not working for existing builds anymore. It seems from looking at the source of the sample action that the "Name"-Attribute in the <action>-Tag was removed. However the name-tag was used in the Visual Build 5.7 .bld-Files to identify the action. In Visual Build 6 it seems the filename is used to identify the action, and thus if those two differ the action is not found. Since we're using a lot of custom actions, this is very annoying.
Is there a way to circumvent this problem, without having to rename all custom actions?

Cheers

Ulf

[kinook]

That was an intentional change; we were hoping nobody was actually using a name differing from the filename :^). And we neglected to mention this compatibility issue in the upgrade help topic. In prior versions, the .action filename (without extension) was used for the action name by default, but this could be overridden by adding a Name attribute to the action element of the .action file. In version 6, the Name attribute is ignored and the filename is always used for the action name.

Attached is a project you can use to convert existing projects for actions that have a Name attribute which differs from the filename. This project will process all .action files in the path where it is saved to identify actions whose Name does not match its filename. Then it will update all .bld files in the same directory from the old to the new action name. To process .action and/or .bld files elsewhere, change the %PROJDIR% value in the 'Process .action files' and 'Process .bld files' steps (and check the recurse flag to process subdirectories).

Hopefully this will be an adequate workaround, as it would be difficult to put that logic back in (significant functionality, such as changes to how actions can be registered/located and the GUI action designer, has been added since the change which depend on the new behavior).