SAPIEN Technologies

The error will also happen with the following code: Add-Type -AssemblyName System.Windows.Forms $FormMain = New-Object System.Windows.Forms.Form Connect-ExchangeOnline As previously stated, the issue is not the code generated by PowerShell Studio. It is a threading issue when running a GUI while att...

From my research, this is a problem with PowerShell v5.1 and the ExchangeOnlineManagement module being version 2.0.4 or later. There is a little we can do to help with this as these are both Microsoft.
The only known fixes are to downgrade ExchangeOnlineManagement or upgrade to use PowerShell 7.

I'm slightly confused by your statement. Are you running build 209 currently? Are you saying this happened from the previous build?

I'm currently testing with build 209 and have been unable to reproduce this behavior. What are your Formatting settings in options:

Can you please provide a screenshot of your Formatting settings in options:

For C# 10, you will need to download .NET 6:
https://dotnet.microsoft.com/en-us/download/dotnet/6.0

With the files present, can you currently see the templates when creating a new file?

From my initial tests, I found the PowerShell variable $HOME in the path of the dll to be the issue. When I put the full path or relative path without the variable, it appears to work as expected. I've filed a bug report with the development team and update you when I have more information.

We are looking into this and will get back to you soon.

[Topic was moved by moderator to PowerShell GUIs forum]

PowerShell 4 is no longer supported by us; we only support PowerShell 5.1 or higher. This means we do not test to ensure our products work with this version of PowerShell.