The name of a script in Composer cannot contain special characters such as colons, or semi colons as the validation of the script will fail. The reason for the failure is that a temporary file gets created in C:\Windows\Temp when validating , and Windows cannot handle those type of characters for a file name.
When you use the Composer find feature for a string in any AppScript (with many results of same string) the results are posted in the "Find Results". When to select these and "go to location" then appscript is validated each and every time.
When trying to validate an AppScript/ModScript using the Validate Script button, Composer hangs and the process has to be ended. I was able to reproduce this in SBM 11.5 and SBM 11.6. This only happens when Composer is running on a Windows 2008 R2 server which is unsupported by SBM 11.5 and 11.6.
The following code is valid vbscript and is used to escape a double quote but when you try to validate it in composer you get the error below. It's hard to read but there are six double quotes total, three on each side of the text variable used.
