After a couple weeks (more than i had originally intended) of testing I have publicly released v3.00 of Terian Image Capture Pro. You can download it from the official website here
Fortunately no additional bugs were uncovered during testing, so the changes remain the same as outlined in a previous blog entry here
Also, this new release is dual code-signed as discussed in this blog entry.
Effective January 1, 2016, Windows (version 7 and higher) and Windows Server will no longer trust new code that is signed with a SHA-1 code signing certificate for Mark-of-the-Web related scenarios (e.g. files containing a digital signature) and that has been time-stamped with a value greater than January 1, 2016. This cut-off date applies to the code-signing certificate itself.
What this means:
Any new distribution of our products (i.e. Terian ICP, Terian IDC) that are code signed and time stamped from 01/Jan/2016 onwards will no longer appear as coming from a verified publisher, i.e. like this…
Fortunately GoDaddy provides both SHA-1, and SHA256 code signing certificates. So newer versions of Windows can be supported with the new SHA256 certificate ensuring our applications still appear to be from a verified published.
Dual Certificate Code Signing:
To ensure we maintain backward compatibility with older versions of windows all new distributions will be code signed with both the SHA-1, and SHA256 certificates, like this…
Once SHA-1 has been fully deprecated we will most likely transition to only signing our code with the SHA256 certificate. Hopefully by this time our requirement to ensure 100% support on older systems will be reduced.
More information regarding Windows Enforcement of authenticode Code Signing can be found here
Just a quick note as I’ve compiled Terian Image Capture Pro v3.00, and will be putting it through testing for the next couple of days hopefully with a public release early next week.
New Capture Library -> Improved Resolution Support:
Our clients expressed the desire to capture at higher resolutions, unfortunately the old framework failed to adequately support higher resolutions with graphical overlays. Whilst a more extensive version of the old framework was available that provided the appropriate level of support the cost to upgrade was similar to the cost of purchasing a license for DataStead VideoGrabber SDK.
I had previously evaluated DataStead VideoGrabber SDK however the cost was beyond our budget at the time, so Mitov BasicVideo Library was chosen. Utilising VideoGrabber also has the advantage of fixing an issue where the preferred capture device and settings are not set correctly on application startup under the old framework.
Testing so far has been positive with the VideoGrabber SDK, and I am confident the performance improvements will allow our clients to capture high resolution images.
If testing progresses well and no major hurdles are encountered, as stated above I hope to release to the website early next week.