I am new to using PowerShell Studio 2017 (or any other version of this product).
I have installed PowerShell Studio 2017 v5.4.136 64bit
On my 64 bit Windows 10 Pro system (10.0.14393.0)
Running PowerShell 5.1.14393.953
I am trying to modify a script that was created using PoweShell ISE. This script contains the following statement:
$osver = [System.Environment]::OSVersion.Version.Major
When I run this on my machine under ISE, I get a version of 10. Under PowerShell Studio, it returns a value of 6. I have the target environment set to V5 - 64bit.
I assume that I have something set wrong in my options but as I have just used the product 3 or 4 times, I cannot figure out what I may have done.
Apologies if I have done something really stupid, and just don't see it.
Newbie question
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Re: Newbie question
No need to apologize, this isn't due to a mistake on your part
This is most likely due to a change in the Windows API that caused some trouble for our applications after Windows 8 was launched as well https://www.sapien.com/blog/2014/04/02/ ... rsion-api/
I've brought this up with the team and we'll make sure this is taken care of shortly, when we have some more information, we'll be sure to post it here.
This is most likely due to a change in the Windows API that caused some trouble for our applications after Windows 8 was launched as well https://www.sapien.com/blog/2014/04/02/ ... rsion-api/
I've brought this up with the team and we'll make sure this is taken care of shortly, when we have some more information, we'll be sure to post it here.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Newbie question
As a new poster I was being extra specially courteous. But I was pretty sure it was an issue with your product.DevinL wrote:No need to apologize, this isn't due to a mistake on your part
This is most likely due to a change in the Windows API that caused some trouble for our applications after Windows 8 was launched as well https://www.sapien.com/blog/2014/04/02/ ... rsion-api/
I've brought this up with the team and we'll make sure this is taken care of shortly, when we have some more information, we'll be sure to post it here.
I hope I can assume that if something works one way under the MS PowerShell ISE, it can be expected to work the same way under your product.
Re: Newbie question
This is mostly true, yes.cheltzel wrote:I hope I can assume that if something works one way under the MS PowerShell ISE, it can be expected to work the same way under your product.
The biggest exception being that the ISE maintains the runspace between the execution of scripts, whereas PowerShell Studio doesn't and resets the runspace before each execution.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Newbie question
That doesn't bother me. I just don't want to worry about doing some heavy development/debugging and then find it doesn't work when the script is run as a script off the command line.DevinL wrote:This is mostly true, yes.cheltzel wrote:I hope I can assume that if something works one way under the MS PowerShell ISE, it can be expected to work the same way under your product.
The biggest exception being that the ISE maintains the runspace between the execution of scripts, whereas PowerShell Studio doesn't and resets the runspace before each execution.
Re: Newbie question
Hey Cheltzel,
I would just like to let you know that we released the fix for this issue in our recent service build.
If you could please update to 5.4.137 and verify it's been fixed for you as well, we'd greatly appreciate it.
I would just like to let you know that we released the fix for this issue in our recent service build.
If you could please update to 5.4.137 and verify it's been fixed for you as well, we'd greatly appreciate it.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Newbie question
I just updated to 5.4.138 and it is fixed.DevinL wrote:Hey Cheltzel,
I would just like to let you know that we released the fix for this issue in our recent service build.
If you could please update to 5.4.137 and verify it's been fixed for you as well, we'd greatly appreciate it.
Re: Newbie question
Glad to hear it!
If you have any further issues, please don't hesitate to post again.
If you have any further issues, please don't hesitate to post again.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.