Enables Amqp_Tcp_Only when running as IoT Edge module.

This release add the following features:

• Allows to use Amqp_Tcp_Only or Mqtt_Tcp_Only when running as IoT Edge module.
• Uses Amqp_Tcp_Only as default protocol when running as IoT Edge module.

Heartbeat/skipfirst/suppressedopcstatuscodes features

This release adds the following features:

• OPC Publisher will be able to generate telemetry events for slow changing or static node value data. For the heartbeat event the telemetry event data value will be the same as the last seen data value (only the SourceTimestamp will be adjusted).
• This functionality can be enabled via a command line option for all nodes or via a node specific configuration.
• OPC Publisher will be able to skip the first telemetry event for a node value. This will prevent a flood of events if a large number of nodes is published.
• This functionality can be enabled via a command line option for all nodes or via a node specific configuration.
• OPC Publisher is able to suppress generation of telemetry events for a configurable set of OPC UA status codes reported by the OPC UA stack when a node value change is reported. This allows to suppress telemetry events when the OPC UA stack reports errors like "BadNoCommunication".
• This functionality can be configured via command line option.

OPC Publisher 2.3.1

This release adds:

• Generic OPC method to call IoTHub direct method implementations
• Detects when running in IoTEdgeHubDev simulator
• Fixes warnings

OPC Publisher 2.3.0

This release adds:

• command line options for certificate management
• allow to set display name of a node via configuration file
• adds direct methods to get diagnostic info

OPC Publisher 2.2.0

This version does support the GA version of IoT Edge and can run standalone as well as an IoT Edge module.

No conversion to ExpandedNodeId for NodeId publishing requests via OPC UA server methods

This release fixes a bug when publishing nodes via OPC UA server method of OpcPublisher's OPC UA server.

Correct Json formatting for ingested data, remove credentials from log files

There are the following changes in this release:

• Change the JSON format of ingested data to use arrays of data objects.
• Suppress logging IoTHub credential information.
• Suppress updating node configuration file with publishing and sampling interval if default settings are used.

Fixes in shutdown mechanics and config file handling

This release has the following changes:

• Publisher now works even if the published nodes configuration file does not exist
• an option have been added to never shutdown
• the shutdown process has been fixed

Refactor publishing path, add diagnostics and update documentation

This release:

• Refactors the publishing/batching part to use a bounded queue instead of an unbounded ConcurrentQueue. This prevents hosts running into memory resource issues and requires reasonable configuration of the send interval and message size parameters to meet the scenario in which publisher is used.
• Documentation has been updated to describe different use cases and parameter settings and how they impact performance and queue utilization.
• An option to show diagnostic information in configurable intervals has been added.

New architecture and .NET Core 2.0 support

The architecture of publisher has been changed to:

• support reconnection support of disconnected OPC servers
• add more configuration options via command line
• remove the OPC model compiler generated server address space configuration and configure it programmatically
• update to .NET Core 2.0
• update other used NuGet packages
• use OPC subscriptions
• support a new configuration file fomat to specify the nodes to publish
• support configuration of the sampling and publishing interval of the nodes to publish