SAPIEN Technologies

Are you packaging your single-form application into an executable before creating an installer? If this is the case, can you provide a screenshot of your settings on the Version Information tab?

If this is not the case, can you copy and paste here the entire output when you attempt to build?

You can prevent the form closing in the FormClosing event. You can set a boolean when you process starts and you can check it on closing: $processFinished = $false #Start your process and when it finishes, set $processFinished to true $form1_FormClosing=[System.Windows.Forms.FormClosingEventHandler]...

Something like the following should work with the assemblies referenced and using the function Get-ScriptDirectory: $webview = New-Object 'Microsoft.Web.WebView2.WinForms.WebView2' $webview.CreationProperties = New-Object 'Microsoft.Web.WebView2.WinForms.CoreWebView2CreationProperties' $userDataFold...

Support for the webview2 control was added in 5.8.201 as you stated. There is no way to get this control in the toolbox prior to this build.

You can manually add the webview2 control via code (from the script tab), but you will not be able to add it from the designer without updating.

Can you confirm if $SAPIENHost.GetPassword(0) is returning anything? You could check with a break point on that line or an output statement.

[Moved to PowerShell GUIs form by moderator]

To clarify, are you saying you are unable to see the bottom-right corner of your form on the laptop?

If so, are you able to see more of the form if you undock panels?

Similar to running a form on a different machine, the form shown in the designer with size based on the display and set properties. This means controls will 'resize themselves' in the designer on different displays.

I apologize for the delayed response.
Is this still an issue for you?

We have seen this behavior before when something is blocking the signing process. Please try signing your executable from a console. This should reveal more helpful information.

Based on my research, this may be happening from conflicting commands:
https://learn.microsoft.com/en-us/power ... -conflicts

Do you have multiple commands named Where-Object or Get-Content from different modules?