Pete

Last month (June 2017) was stressful for the general community, our customers and us as the June Security Update from Microsoft included a bug in Internet Explorer that led to a breakage in printing, the impact of which maybe took everyone by surprise. On the Thursday morning we received a report of printing problems from a customer that they suspected was due to the security update (well spotted them!). Generally our first reaction in these cases is that a change has occurred…

Hotfix Release 8.0.1 fixes some issues with printHtml(). It also fixes being unable to remove the PDF printing extension if ScriptX was removed first and there is a minor performance and stability improvement when printBackground is not used. All files are now signed according to the latest signing standards. A full listing of the issues addressed is available in the Knowledge Bank. As usual with hotfixes, you only need to upgrade to this release if you are affected by any…

In October I talked about v2 of our helper libraries for helping to add control of printing to sites/apps developed with ASP.NET and that they referenced v8 of ScriptX. Back then it was still in beta. ScriptX 8 is now released to complete the puzzle. ScriptX 8 is designed for and requires Internet Explorer 11. We have removed support for older browsers and removed support for Windows XP and Windows 2000. For these environments ScriptX 7 continues to be available…

Version 2.0.0 of MeadCo ScriptX Helpers for ASP.NET MVC is now available on Nuget and Github. Also available is version 2.0.0 of MeadCo.ScriptXConfigurationHandler, also on Nuget and GitHub. All code is available under the MIT Open Source License. If you don’t know what these helpers are and how they can help then take a look at our quick introduction that uses v1. These are the next two pieces of our ScriptX 8 puzzle. We are working towards this release with…

Version 1.1.0 of the javascript helper for ScriptX is now available on Nuget. Full source is available on GitHub. The library provides wrappers on common functionality and has proved to be very popular with many developers deploying ScriptX to provide controlled and consistent printing from Internet Explorer on Windows. Version 1.1 has a new implementation of the namespaces MeadCo and MeadCo.ScriptX. The new implementation allows extension of the namespace so that we can provide additional functionality in the future. The implementation…

All the samples described in the Guide for Printing in Applications are now available on GitHub. These illustrate how to print html from a .NET c# WPF desktop application that uses a WebBrowser control to display HTML.

We recently added a sample on using ScriptX within a console application to print html content downloaded from arbitrary urls. The sample contains some interesting utility code of using callbacks from the PrintHtmlEx() method and also code for wrapping the use of Security Manager and ScriptX. Although a little overkill in a console application these wrappers are useful in services. We are continuing to work on improving our documentation on using ScriptX in services/applications and also to provide more sample…

On 1st January 2016 Microsoft Windows will change how it enforces Authenticode code signing as explained fully in the article “Windows Enforcement of Authenticode Code Signing and Timestamping“. We have been code signing all of the component DLLs in ScriptX since long before it became a requirement/recommendation as well as the .cab/.msi file wrapping the installation We will be releasing ScriptX 7.7 before the end of 2015. This release will be signed and time stamped with an SHA-1 certificate and so…

The recent hotfix to ScriptX has fixed an issue with selecting a paper size. We try and be as helpful as we can in matching the string describing the papersize to those available but the algorithm had a problem when there are multiple matches for the requested name and longer names come before shorter matching names – it would match the long name. So, for example you request “A3” and there is a paper size “A3 – Large” that enumerates before…

This error can occur when deploying a new or updated MeadCo Security Manager license for ScriptX. What it means is there is a mismatch between a parameter given on the Security Manager object and the downloaded license file. Either: The GUID parameter given in the Security Manager object does not match. The revision value in the downloaded license file is less than the revision parameter (for example <param name=”revision” value=”4″ /> and the value in the downloaded license file is “3”.…