What’s New in QuickOPC 5.30

Key changes:

• OPC Certification
• .NET Framework 4.5

Conformance

• QuickOPC is officially certified by OPC Foundation for “UA Generic Client” profile (UA CTT 1.02.0.164), Serial Number 1312CS0045, http://www.opcfoundation.org/Default.aspx/certifiedproduct.asp?MID=Compliance&certificate=1312CS0045, http://www.opcfoundation.org/Default.aspx/CertifiedProducts.asp?MID=Compliance .

• The default settings of QuickOPC are set for best interoperability. If you require best OPC compliance, do one of the following:

a) Set the static property EasyUAClient.AdaptableParameters to EasyUAAdaptableParameters.OpcCompliance. This will influence all newly created EasyUAClient instances that have their Isolated property set to false (the default).

b) On a newly created EasyUAClient instance, set the Isolated property to true, and set the IsolatedAdaptableParameters to EasyUAAdaptableParameters.OpcCompliance. This will influence this particular EasyUAClient instance only.

Technologies

• .NET Framework 4.5 is now the primary/minimal target for QuickOPC.NET development.
• Visual Studio 2012/2013 are now the targeted development tools with QuickOPC.NET.
• .NET code access security now uses the Level 2 transparency model.
• COM: Unchanged – any development tool capable of COM development can be used. For Microsoft tools, this should mean Visual C++ 6.0 or later, although we do not test for it specifically, and Visual Studio 2012/2013 is used for verification.

Packaging

• Separate Microsoft.Contracts assembly is no longer needed.
• Separate assemblies for functionality available only with .NET 4 are no longer needed.

Deployment

• Different Visual C++ redistributables (Visual C++ Redistributable Packages for Visual Studio 2013) are now needed.
• COM: Visual C++ redistributables are no longer needed for QuickOPC-COM deployments.

User Interface

• In QuickOPC-UA, by default, user notifications (such as certificate validation error, or domain name mismatches) are now shown in one common dialog, allowing multiple notifications be processed at the same time. The old behavior (each notification is shows its own dialog) is still available. The controlling parameter is UAClientEngineParameters.UseParallelNotifier.
• Various browsing dialogs have been enhanced by splitters, i.e. the user can now resize parts of the dialogs by moving the splitters as needed.
• The properties of OpcBrowseDialog (for OPC “Classic”) have been grouped into Mode, Inputs, InputsOutputs, and Outputs objects.
• The properties of UABrowseDialog (for OPC Unified Architecture) have been grouped into Mode, Inputs, InputsOutputs, and Outputs objects.

Examples

• Visual Studio examples are now mainly provided for Visual Studio 2012. They can be automatically converted to Visual Studio 2013.
• Earlier separate examples for .NET 4 were merged into the regular example projects/solutions.
• Examples for reactive programming model have been separated into a dedicated solution, because they need an installation of Microsoft Reactive Extension.

Removed

• COM: The bonus OPCItemGen application has been removed.
• COM: The “Portable” examples have been removed.