Support Forums

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.

AFAIK code signing certificates are always per organization or user. Never per machine.

I am not sure what certificate you have there, but it sounds like you are using a website certificate. What you need is a code signing certificate. There is a very important distinction between code signing certificates and simple TLS/SSL certificates. We can not recommend or endorse any one vendor,...

All these will work with PowerShell Studio, as any code signing certificate. The issue is where it will be trusted.
In general, if you want to distribute software to the general public you should go with what has the highest built-in trust level.