Unfortunately we have no control at this point what the WScript object reports, since it is the genuine Microsoft Windows Script Host which runs the script.
I'll make a note of it and see what we can do in future versions.
Alex
Search found 8476 matches
- Wed Feb 14, 2007 7:15 am
- Forum: PrimalScript
- Topic: EXE scriptfullname
- Replies: 6
- Views: 3764
- Wed Feb 14, 2007 6:15 am
- Forum: Former and Future Customers - Questions
- Topic: Error when code signing VBS script
- Replies: 11
- Views: 11812
Error when code signing VBS script
Does the script still work when you leave the last parameter off?
Set objSigner = WScript.CreateObject("Scripting.Signer")objSigner.SignFile "C:ScratchScriptTosign.vbs", "SANtools, Inc."
Set objSigner = WScript.CreateObject("Scripting.Signer")objSigner.SignFile "C:ScratchScriptTosign.vbs", "SANtools, Inc."
- Wed Feb 14, 2007 5:40 am
- Forum: Former and Future Customers - Questions
- Topic: Error when code signing VBS script
- Replies: 11
- Views: 11812
Error when code signing VBS script
PrimalScript uses Microsoft's Script Signer component to sign scripts. It is not impossible that this simply does not work under a 64bit OS. Try to run the script used in this article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/aff04355-a7fe-4670-9ddb-226c712a262e...
- Wed Feb 14, 2007 4:27 am
- Forum: Former and Future Customers - Questions
- Topic: AutoIndent
- Replies: 2
- Views: 4038
AutoIndent
Actually automatic indentation is supported, just not for all languages.
All C-style languages (Javascript, ActionScript etc) are supported by this,
VBScript unfortunately is not supported by this yet.
Alex
All C-style languages (Javascript, ActionScript etc) are supported by this,
VBScript unfortunately is not supported by this yet.
Alex
- Tue Feb 13, 2007 7:25 am
- Forum: Customer Service
- Topic: Installation Error
- Replies: 3
- Views: 3092
Installation Error
Please send it to support@sapien.com
- Tue Feb 13, 2007 2:33 am
- Forum: Former and Future Customers - Questions
- Topic: PrimalScript 4.1 problems with Powershell
- Replies: 10
- Views: 8039
PrimalScript 4.1 problems with Powershell
If you already have the acurate PowerShell version,
try to run Regasm on PWSHHelpCtrl.dll in the PrimalScript installation folder.
Please note that your should use the .NET 2.0 version of RegAsm.
try to run Regasm on PWSHHelpCtrl.dll in the PrimalScript installation folder.
Please note that your should use the .NET 2.0 version of RegAsm.
- Mon Feb 12, 2007 6:51 pm
- Forum: Former and Future Customers - Questions
- Topic: PrimalScript 4.1 problems with Powershell
- Replies: 10
- Views: 8039
PrimalScript 4.1 problems with Powershell
Your PowerShell.exe file version should be 6.0.5430.0 (or higher) The file is usually located here: C:WINDOWSsystem32windowspowershellv1.0 If on your computer you do NOT have this version, the PowerShell interface dll did not install correctly. Please install the RTM version of PowerShell, then re-i...
- Mon Feb 12, 2007 6:19 pm
- Forum: Former and Future Customers - Questions
- Topic: PrimalScript 4.1 problems with Powershell
- Replies: 10
- Views: 8039
PrimalScript 4.1 problems with Powershell
Which build of PrimalScript do you have and please also include the exact version number of powershell.exe on your machine.
Alex
Alex
- Mon Feb 12, 2007 1:09 pm
- Forum: Former and Future Customers - Questions
- Topic: PrimalSense in include file
- Replies: 11
- Views: 12016
PrimalSense in include file
The links actually go nowhere. We have not been able to determine what actually is supposedly wrong. If you have any specific examples of what is not shown correctly we are more than happy to look. Please send an example project with your files (zipped) to support@sapien.com and we will most certain...
- Mon Feb 12, 2007 8:17 am
- Forum: Customer Service
- Topic: Installation Error
- Replies: 3
- Views: 3092
Installation Error
That seems (after brief Google search) to indicate a problem with your .NET framework installation.
Does it say which file?
Alex
Does it say which file?
Alex