Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts. Register and secure your Critical IT infrastructure
Log File Generation with the .Net API
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
The .Net API, introduced in ClearSCADA 2009 R1, is a programming interface that can be used to connect to the ClearSCADA server allowing client applications to perform monitoring, control or configuration of the ClearSCADA database. The .Net API is provided as an alternative to the COM based Automation Interface.
The documented and supported .Net API is handled through ClearScada.Client.dll.
Interface Logging
For the COM based Automation Interfaces, DBClient records a set of low level communications logs describing the interface activity between the data access components on the client and the server. This functionality is implemented by default within the DBClient.dll and is enabled or disabled via registry settings (see DBClient Logs).
In the .Net interface you are recommended to use nlog (the same version shipped with Geo SCADA). Some communications logging will then be logged to the file you specify in your nlog settings. The implementation of this requires the calling client application to actively initialize the logging to specify an output path. No default registry settings are available for enabling and disabling of these logging classes. Go: HomeBack