KNOWN ISSUE: Variables are no longer updated in debugger after an include script is called
|Article:TECH29525|||||Created: 2007-05-04|||||Updated: 2008-04-02|||||Article URL http://www.symantec.com/docs/TECH29525|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
While running a WiseScript in debug mode, after an include script is called, variables are no longer updated in the variable list.
Steps to reproduce:
- Create an include script name include.wse. It doesn't matter what is in the script.
- Add the following code to a blank script:
Set Variable TEST to 1
Set Variable TEST to 2
Include Script <path to include.wse>
Set Variable TEST to 3
- Run this code through the debugger:
When the line Set Variable TEST to 1 is executed, the value of TEST is added to the list of variables and has a value of 1.
When Set Variable TEST to 2 is executed, the value in the list is updated to 2
When Set Variable TEST to 3 is executed, the value in the list of variables is not updated at all.
Wise Package Studio 7.x
Wise Installation Studio 7.0
There is no resolution or workaround at this time. Symantec is working towards a resolution and will update this article when a resolution is reached. Subscribe to this article if you would like to receive any updates.
To assist with debugging a WiseScript installation that contains include scripts, you can use Display Message actions to determine the value of specific variables.
|Description||Logged in Littlebuggy (Altiris - Lindon, Plymouth) database|
Article URL http://www.symantec.com/docs/TECH29525