Could you please reset my activations for the two products purchased on April 22, 2017? I had a hard disk failure and wasn't able to unregister.
Thank you.
Search found 20 matches
- Sun Jul 23, 2017 10:24 am
- Forum: Customer Service
- Topic: Activation reset
- Replies: 1
- Views: 4560
- Fri Jun 09, 2017 7:22 am
- Forum: PowerShell Studio
- Topic: Activation server cannot be reached
- Replies: 1
- Views: 1229
Activation server cannot be reached
Product, version and build: 5.4.140_051817_x64 (*** Please do not write "latest" as a version, specify a version number ***) 32 or 64 bit version of product: 64 Operating system: Windows 10 32 or 64 bit OS: 64 PowerShell Version: 5 I am unable to activate my software. My network connection...
- Sun Dec 11, 2016 6:19 am
- Forum: PowerShell Studio
- Topic: Why doesn't $PSScriptRoot resolve properly in PSS?
- Replies: 7
- Views: 7529
Re: Why doesn't $PSScriptRoot resolve properly in PSS?
I know this. It seems to me it would be a minor fix for you to change the default populated in that dialog with the actual path (or relative path, as I've been doing), when it appears. This would be a better solution than telling your customers to use a workaround. I'm sorry to sound antagonistic bu...
- Fri Dec 09, 2016 11:56 am
- Forum: PowerShell Studio
- Topic: Why doesn't $PSScriptRoot resolve properly in PSS?
- Replies: 7
- Views: 7529
Re: Why doesn't $PSScriptRoot resolve properly in PSS?
The problem is with the pop-up box that prompts for parameters when running from the program. $PSScriptRoot translates correctly in the script when it's used. The issue is entering the value as a parameter in the popup. I have a script that the default location for the file is in $PSScriptRoot. When...
- Fri Dec 09, 2016 8:47 am
- Forum: PowerShell Studio
- Topic: Why doesn't $PSScriptRoot resolve properly in PSS?
- Replies: 7
- Views: 7529
Why doesn't $PSScriptRoot resolve properly in PSS?
Product, version and build: PowerShell Studio 2016 v.5.3.131 (*** Please do not write "latest" as a version, specify a version number ***) 32 or 64 bit version of product: Operating system: Windows 8.1 32 or 64 bit OS: 64-bit PowerShell Version: 4 When I debug scripts that include referenc...
- Fri Sep 16, 2016 10:29 am
- Forum: Customer Service
- Topic: Activation reset needed
- Replies: 4
- Views: 2499
Activation reset needed
I was terminated from my previous job suddenly and was unable to uninstall my copy of PowerShell Studio 2016. My activation details indicate that I cannot reset it until November 16th and I have started my new job and need to install the software. Please reset my PowerShell Studio license count. Tha...
- Tue Jun 07, 2016 11:06 am
- Forum: PowerShell Studio
- Topic: PowerShell Studio 2016 Debugging Broken
- Replies: 9
- Views: 5535
Re: PowerShell Studio 2016 Debugging Broken
I did some experimenting and discovered that if I load the script file alone without the project file, the debugger will stop at breakpoints. It's only when I load the project with the file as a member that the issue occurs.
- Tue Jun 07, 2016 10:19 am
- Forum: PowerShell Studio
- Topic: PowerShell Studio 2016 Debugging Broken
- Replies: 9
- Views: 5535
Re: PowerShell Studio 2016 Debugging Broken
I have uploaded the project file. The module file is where several of the functions I used in the script reside. I included it in case you wanted to run the script. I have also discovered that simple scripts will stop at breakpoints but that as the script gets longer, the debugger stops working prop...
- Mon Jun 06, 2016 6:22 am
- Forum: PowerShell Studio
- Topic: PowerShell Studio 2016 Debugging Broken
- Replies: 9
- Views: 5535
Re: PowerShell Studio 2016 Debugging Broken
The file is the only file (script or otherwise) in a project with the same name. The problem happens in the file I uploaded but not in others. I created a new script that does nothing but open an Open File Dialog box. The breakpoint works fine in this file. I don't do anything unusual when loading t...
- Fri Jun 03, 2016 6:10 am
- Forum: PowerShell Studio
- Topic: PowerShell Studio 2016 Debugging Broken
- Replies: 9
- Views: 5535
PowerShell Studio 2016 Debugging Broken
Product, version and build: PowerShell Studio 2016 5.2.122 32 or 64 bit version of product: 64-bit Operating system: Windows 10 32 or 64 bit OS: 64-bit PowerShell Version: 5.0 Just upgraded from PSS2015 to PSS2016 and discovered that debugging is broken. Found another topic about people unable to cr...