OPC Studio User's Guide and Reference
Best Practices
Client and Subscriber Development > Best Practices

This section describes best practices that aid in developing applications and libraries that use the QuickOPC library.

All information described in this section is merely a set of guidelines to aid development. These guidelines do not constitute an absolute truth. They are patterns that we found helpful; not rules that should be followed blindly. There are situations where certain guidelines do not apply. It is up to each individual developer to decide if a certain guideline makes sense in each specific situation.

The guidelines in this section are listed in no particular order.

See Also
Do not write any code for OPC failure recovery
With single-operation synchronous methods, only catch OpcException or UAException
Do not catch any exceptions with asynchronous or multiple-operation methods
Always test the Exception property before accessing the actual result (Value, Vtq, or AttributeData property)
Always test the HasValue property before accessing DAVtq.Value or UAAttributeData.Value
Use multiple-operation methods instead of looping
Do not block inside OPC event handlers or callback methods
Use generic or type-safe access wherever possible
Use the state instead of handles to identify subscribed entities
Development Models

Knowledge base

Category:Coding techniques

 

 

Copyright © 2004-2024 CODE Consulting and Development, s.r.o., Plzen. All rights reserved. Web page: www.opclabs.com

Send Documentation Feedback. Resources: Knowledge Base, Product Downloads. Technical support: Online Forums, FAQ.

Missing some example? Ask us for it on our Online Forums! You do not have to own a commercial license in order to use Online Forums, and we reply to every post.