Support Forums

That's because the files are not signed. You can keep them, of course. You may have to remove them manually if the next update does not replace them automatically and re-install. Sorry for any inconvenience.

Are you by any chance having STA mode checked when debugging?

Download this file: https://sapien.s3.amazonaws.com/downloads/Support%20files/ScriptDebugger%202019.zip Replace the files here with the content of the zip: C:\Program Files (x86)\Common Files\SAPIEN Debugger 2019 Please make a backup of the original files first and let us know if this solves the pro...

Please see https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_reserved_words?view=powershell-6 The keyword type is in the list of reserved words and is therefore correctly case corrected to the indicated case used in the documentation. From the documentation: "T...

The MSI builder is only invoked when PSBuild has an /MSI parameter, which can only happen if you select to build the MSI file. As these items are all enabled just simply if a settings file exists, it might be possible to hit them accidentally. Therefore the next service build will enable/disable opt...

Please try to uninstall and re-install PowerShell Studio. That should re-register the COM objects missing.

We have a handle on it. Next service build...

Please send or upload the .psbuild file for the file that exhibits the MSI error when packaging an exe.

Sometimes Windows installer gets confused. See if you can manually uninstall from "Add / remove programs"

I'll look into it but as far as I know there is no size limit imposed by us.