Variables/string parsing not assigning properly on WS2008
Posted: Wed Mar 14, 2012 9:19 am
Has anyone run across an issue with strings and variable assignments not working correctly on Windows Server 2008 Standard 32 bit? I have one customer's system which the installer was not properly parsing the $TITLE$ or apparently other assignments using that $<Variable Name>$ method.
The symptom was the dialog screens instead of showing the value of the variable instead shows $TITLE$ in the captions but it appeared to be elsewhere also as it was generating errors about "" not being a valid integer value. But the line number that was shown in the error made no sense as at that line in the main script is a comment. I am guessing the line number doesn't directly relate to the main script when include scripts are being used?
I tested placing a messagebox at the start of the script and that did parse correctly, but again once it got to the dialog screens it was still showing incorrectly. So somewhere between the start of the project and the user interview it is stopping. This same script/generated executable works properly on other test systems I have in house though so I can't duplicate the issue on a system that I can debug.
I know this isn't much to go one, but was hoping someone may have seen similar behavior before.
Thank you,
Chris
The symptom was the dialog screens instead of showing the value of the variable instead shows $TITLE$ in the captions but it appeared to be elsewhere also as it was generating errors about "" not being a valid integer value. But the line number that was shown in the error made no sense as at that line in the main script is a comment. I am guessing the line number doesn't directly relate to the main script when include scripts are being used?
I tested placing a messagebox at the start of the script and that did parse correctly, but again once it got to the dialog screens it was still showing incorrectly. So somewhere between the start of the project and the user interview it is stopping. This same script/generated executable works properly on other test systems I have in house though so I can't duplicate the issue on a system that I can debug.
I know this isn't much to go one, but was hoping someone may have seen similar behavior before.
Thank you,
Chris