Migrating to WebClientPrint 5.0 for ASP.NET Core, MVC & WebForms
Product WebClientPrint for ASP.NET Published 10/08/2019 Updated 10/08/2019 Author Neodynamic
The brand new WebClientPrint 5.0 for ASP.NET is compatible with Version 4.0 but a few modifications must be done to get v5.0 working on an existing project using v4.0. There are also some breaking changes to be considered when moving to v5.0. Please use this article as a general guide to upgrading your server-side code to v5.0
In this article:
- WebClientPrint Assembly Update
- WebClientPrint Processor (WCPP) Update
- SerialPortPrinter class Update
• WebClientPrint Assembly Update
In your project where old v4 is being used and you want to upgrade to v5, then UPDATE the WebClientPrint dll assembly to latest v5. Do it by downloading the package installer from our website's Download section or from Nuget
WebClientPrint is now built as a .NET Standard 2.0 Lib which means that ASP.NET 2.0 and 3.x are no longer supported!. Being a .NET Standard Lib, now there's a single WebClientPrint dll that can be used/referenced in classic/legacy ASP.NET WebForms and ASP.NET Core MVC. The minimum supported ASP.NET non-Core version is 4.6.1
• WebClientPrint Processor (WCPP) Update
Any project using WebClientPrint assembly v5 will require that ANY Client that wants to print from them, to install WebClientPrint Processor (WCPP) v5 which can be downloaded and installed from our website's Download section
32-bit WCPP for Mac and Linux are no longer supported! Only 64-bit WCPP apps are supported under macOS and Linux.
• SerialPortPrinter class Update
SerialPortPrinter class does not longer references to System.IO.Ports enums for related properties and were changed to similar enums part of WebClientPrint assembly.
System.IO.Ports.Handshake, System.IO.Ports.Parity, and System.IO.Ports.StopBits must be changed by
SerialPortHandshake, SerialPortParity, and SerialPortStopBits respectivelly.
That's all. Just be sure that your project is now referencing new v5.0 of WebClientPrint assembly.
As always, do not hesitate to contact our dev team at http://neodynamic.com/support