SAPIEN Technologies

PowerShell 7.1 is not supported yet. It uses the new .NET 5.0. Basically it means we need to rebuild, recompile and retest everything, which takes time.
It will be supported in an upcoming service release.

If you have no error output when signing, the authenticode API has nothing to object to. Meaning that the signing and time stamping was successful as far as it is concerned. When you say you check the exe it is not signed, how exactly are you checking it? Diagnosing authenticode issues in an air-gap...

Thank you for following up!

Once again, this is not a general PowerShell forum. Please post in the appropriate forum with a detailed description of what you are trying to accomplish and what you have already tried.

Just add your produced exe to the list of files included in the MSI. That's not mind boggling complex, it just puts the user in control what gets added to the MSI. I understand that, if all you want is to create an MSI your packaged exe with a few other files, any extra step may seem somewhat superf...

I completely understand how frustrating this must be. Not having access to your computer, I can only tell you from what in my experience usually causes this type of problem. I don't know if this is your own personal computer or a corporate computer, so I do not know who else can influence things. If...

That means that likely you have screwed up folder permissions somewhere.

This is a wishlist and feature request forum for SAPIEN products. I am not really sure what it is you are trying to accomplish and how it relates to our products. That makes it hard to recommend a different place for you. I would recommend a general powershell place and to be much more verbose about...

I am glad you found a solution. While the Windows Forms packager engine (I assume that is what you used) does not use a Visual Studio runtime, any modules and .NET types you load in your script might. It is not possible from your description to determine what actually caused this error. But in gener...

The packager can already sign the resulting exe every time you build. Just in case that got lost somewhere.
I will consult with the development team what the status of this is.