The latest service build of PrimalScript 2011 (6.0.134) is now available from MySAPIEN for registered users.
This build includes the following fixes:
- An encoding related XML or HTML rendering problem caused PrimalScript to hang loading certain files.
- Check for updates does not see PS2011
- Dynamic help not operational on mouse click selection
- Named parameters starting with – or / characters where not handed to the script engine in some instances.
- Installer did not update prerequisites to newer versions
- Credentials in PowerShell packages not handled correctly in some instances.
- Profile Manager did not launch PrimalScript or open files correctly.
- Script Packager reported missing license on some machines.
- Running a script in a PowerShell console now uses .”script” rather than &”script” to preserve settings after script terminates.
- SAPIEN Document Explorer did not add imported PowerShell snapins correctly to the index.
The following items have been added:
- PowerShell cmdlets and aliases are now cached per platform. Your first start will be a bit slower than usual as the cache files are built. PowerShell no longer needs to be loaded to just edit a file.
- The VMWare PowerCLI documentation in the SAPIEN Document Explorer was updated to the latest version.
- After a PowerShell script is finished or terminated in the debugger the last known state of all variables (if available) is submitted to the debug window.
