SAPIEN Technologies

FYI, we are running sale:

https://www.sapien.com/blog/2019/07/03/ ... -60-years/

Hopefully that will help!

Sorry, I did not notice you were using 2016. This template is included in the 2019 version. You can try looking at this topic thread:

viewtopic.php?f=21&t=12969&hilit=redire ... t&start=10

It was the inspiration for the template.

This article may be of assistance to you:

https://info.sapien.com/index.php/guis/ ... i-displays

I recommend looking at the Text Box - Redirect Process Output form template.

It allows you to run an external executable and the output is redirected to the TextBox control.

Yes, we use the term PrimalSense. At this time, our dot sourcing PrimalSense does not collect the variable information. I highly recommend submitting a feature request here:

https://sapien.com/requests

Do you mean validate the signature or the certificate itself?

The application doesn't have a feature to validate the certificate or the signature at this time.

It seems the tokenizer might have hiccupped while editing. When you modified the line near the end of the here string, it corrected the issue by finding the actual end of the here string.

We will keep an eye out.

Thank you for the additional information. This is very strange and have been unable to reproduce it so far. We will update you as soon as we have more details.

There is no password field at this time for the signing process. I recommend submitting a feature request here:

https://www.sapien.com/requests

That way we could address it in a future release.

When PowerShell Studio runs a syntax check, it only does it for the open file. That is why PowerShell reports that it can't resolve the type.

Maybe we could filter out these false errors in a future build.