Benefits

From OPC Labs Knowledge Base
Revision as of 11:20, 28 January 2018 by User (talk | contribs) (→‎Notices)


Support

  • We respond to every post on our Online Forums (http://www.opclabs.com/forum/index).
  • As opposed to many other vendors, our technical support is public, which means that any possible issues are visible on the Web and you can find them - and an advise on how to resolve them - without having to become a customer first. If your issue involves sensitive or confidential information, we can provide support to you via email.

Costs

  • no need to pay yearly to OPCF to stay closed-source. It gets cheaper to purchase the toolkit rather than paying annual OPC Foundation fees.

Developer Friendliness

Notices

  • CLS-compliant
  • data type inference in OPC UA Writes
  • formatting feature
  • debugger: does not show unnecessary private fields
  • automatically adjusts UA timing to debugger
  • connectivity explorer
  • Help integration
  • Comprehensive Reference
  • Intellisense
  • Interoperability tested
  • Visual binding
  • Binary/xml serialization
  • Typesafe (strong typing)/generics
  • "Made for .NET"
  • Low-ceremony API
  • Highly intuitive toolkit
  • .NET and COM interfaces are largely identical
  • API has high expressive power
  • OPC DA Quality Decoder included
  • Excel integration
  • Perpetual license
  • Simple licensing - no hassles with lost licenses "tied" to a hardware
  • no config files necessary - just reference an assembly
  • Pre-installation of OPC Core Component not required
  • Pre-installation of UA Certificate Generator not required
  • No need to create/assign a certificate by a manual process
  • namespace URIs can be specified, not indices
  • any node/item descriptor can specify either a node ID, or browse path, or both
  • UA complex data
  • NuGet
  • app. deployment fully documented, and production installer that actually works (and does not install into undocumented directories etc.)
  • stable product build process
  • no need to pay early to OPCF to stay closed-source
  • slow down UA keep-alive mechanisms when debugging
  • method overloads for short code
  • clear exception model
  • assemblies have strong names
  • our installable and all bineries are code-signed (some security environments do not allow any unsigned code; OPCF does not sign).
  • see/link with http://www.opclabs.com/products/quickopc/features
  • see/link with http://www.opclabs.com/products/quickopc/features/developer-productivity