Search found 4813 matches

by davidc
Fri Aug 04, 2017 8:05 am
Forum: PowerShell Studio
Topic: PowerShell Studio 2012 - Installer Stuck At PreReq's
Replies: 2
Views: 79

Re: PowerShell Studio 2012 - Installer Stuck At PreReq's

PowerShell Studio 2012 was created before Windows 10 existed, so it is possible that it is a compatibility issue. I recommend unchecking all the optional features before installing the software to see if that helps.
by davidc
Thu Aug 03, 2017 2:04 pm
Forum: PowerShell Studio
Topic: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"
Replies: 8
Views: 137

Re: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"

The error is originating in the UI library. On which panel are you moving your mouse over?

And did you try resetting the panel layout and disabling the auto-layout feature?
by davidc
Thu Aug 03, 2017 12:12 pm
Forum: PowerShell Studio
Topic: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"
Replies: 8
Views: 137

Re: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"

Can you copy the follow text of the exception message?

Please try disabling auto-layouts in the status bar:
Auto-Layout - Status Bar.png
Auto-Layout - Status Bar.png (4.78 KiB) Viewed 115 times
You can also try resetting the current layout in (Options->Panels->Panel Layout->Reset To Default State):
Options - Reset to Default State.png
Options - Reset to Default State.png (24.75 KiB) Viewed 115 times
Thank you,
by davidc
Thu Aug 03, 2017 11:44 am
Forum: PowerShell Studio
Topic: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"
Replies: 8
Views: 137

Re: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"

Sorry it should be:

C:\Users\(username)\AppData\Roaming\SAPIEN\PowerShell Studio 2017\ErrorLog.txt
by davidc
Thu Aug 03, 2017 11:27 am
Forum: PowerShell Studio
Topic: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"
Replies: 8
Views: 137

Re: Debug Error - Cannot access a disposed object. Object name: "Dock Panel"

Please check if there is a log in the following location:

C:\Users\(username)\AppData\Roaming\SAPIEN\PowerShell HelpWriter 2017\ErrorLog.txt

And attach it to this post.

Thank you,
by davidc
Thu Aug 03, 2017 8:32 am
Forum: PowerShell GUIs
Topic: Add second form to a Non-Multiform Project
Replies: 2
Views: 78

Re: Add second form to a Non-Multiform Project

To comply with PowerShell best practices, we changed the Call verb to Show.

So it should now be:

Show-FormName_Extension

Refer to this article for more details:

https://www.sapien.com/blog/2016/11/15/ ... -v5-3-130/
by davidc
Thu Aug 03, 2017 7:53 am
Forum: PowerShell Studio
Topic: MySql.Data.MySqlClient.MySqlCommand ERROR
Replies: 3
Views: 80

Re: MySql.Data.MySqlClient.MySqlCommand ERROR

Please update to the latest build (v5.4.143) and let us know if the issue persist.
by davidc
Wed Aug 02, 2017 2:50 pm
Forum: PowerShell Studio
Topic: Compiled Code Object Reference Error
Replies: 6
Views: 140

Re: Compiled Code Object Reference Error

Unfortunately, we can't compile the script into a true binary executable. The PowerShell engine still requires us to pass the script in order to run it.
by davidc
Wed Aug 02, 2017 7:34 am
Forum: PowerShell Studio
Topic: Sapien PowerShell Studio Packager
Replies: 3
Views: 177

Re: Sapien PowerShell Studio Packager

Unfortunately including the config file is necessary. The config file allows the executable to use other .NET versions if necessary. It also allows older modules / assemblies that were built with .NET 2.0 to work in later versions of .NET.
by davidc
Wed Aug 02, 2017 7:30 am
Forum: PowerShell Studio
Topic: Compiled Code Object Reference Error
Replies: 6
Views: 140

Re: Compiled Code Object Reference Error

They are invoked differently. The packager runs the script from memory where as a normal script runs directly from the file, which PowerShell internally is handling differently. I wish I had a better answer, but unfortunately, I don't have intimate knowledge of PowerShell inner workings.