Commit Graph

8 Commits

Author SHA1 Message Date
Martin Regen 39dca2c103 Complex Types client library (#849)
Adds a complex type system client library extension for custom enumerations and structure types based on a server dictionary or DataTypeDefinition using emitted classes at runtime. 

- Custom types are added to the session factory, not to the global factory. Types are loaded when the session connects by adding 
`                var complexTypeSystem = new ComplexTypeSystem(session);
                await complexTypeSystem.Load();
`
- Custom type properties can be accessed with an accessor [propertyname] or [index]. Direct access through the properties is possible, but some cases do not update the optional or union flags correctly.
- Support includes V1.03 dictionaries and V1.04 DataTypeDefinitions (--> known issues).
- NetCoreComplexClient can be used for quick testing servers. It prints out all custom types with content and subscribes to all. Also includes sample how to write back complex type variables and how to output JSON.
- The UA Sample Client and the Quickstart Data Type client can be used for testing with UI. Many issues were adressed to be able to read and write complex types, however some support is limited, e.g. only editing simple fields is currently working (help wanted).
- Caveat: The complex type libaries for .Net Core must be built for .netcoreapp, so it needs a seperate nuget package for the complex type client extension.
- Support for a factory type builder class to allow to plugin other type builder methods (e.g. Codedom etc...)
- Added JSON test case and include the complex types client in the testing shell script, so the complex types lib is tested on mac/linux too.
- Few fixes in the JSON encoder.

Finding enough servers with custom types is an issue, so if you find servers with unsupported custom types please provide feedback.

Known limitations:
- Only V1.03 OPC binary dictionaries are supported (no XML Schema dictionaries).
- V1.03 dictionary structure definitions are only supported if they can be mapped to a V1.04 DataTypeDefinition. Nested types and cross dictionary refs should work.
- OptionSet is only partially implemented. Only shows the byte arrays, not the flags.
- Opaque Types in dictionaries are ignored.
2019-11-20 16:05:24 +01:00
AlinMoldovean 8b374a7448 Copyright year set to 2019 in license notices. 2019-02-14 12:34:33 +02:00
Martin Regen 5063ac0907 Console client improvements (#343)
* use config file for console sample
* filter unsupported security policies
* add reconnect handler
2018-02-06 14:15:16 +01:00
Martin Regen 2acfcc0a30 add mono client test 2018-01-12 15:09:00 +01:00
Martin Regen d2566c60bd X509store mac fix and travis improvements (#264)
* X509store mac os (#31)

* Fix problem when X509Store CurrentUser\\UA_MachineDefault cannot be created on macOS with .NetStandard2.0
Fix: Use CurrentUser\My instead for all machine certs to make console apps portable.

* prep console sample apps for smoke test
* update travis image
* run sample server and client as smoke test


* ignore travis osx build failure until travis is fixed
2017-10-12 11:16:09 +02:00
Martin Regen d850f64f81 Support .netstandard2.0 (#237)
* add missing ref for build in VSO hosted VS 2017 build

* project to just build Dlls

* target multiple frameworks

* switch to net46/netstandard1.3

* fix projects to allow for netcoreapp 2.0 build

* fix networking for .Net Core 2.0:
SendAsync and ReceiveAsync now frequently return synchronously even if successful. These cases had not been properly handled yet, previous versions never hit these codepaths.

* fix travis build / nugets

* change travis build target

* fix Kestrel https option for netstandard 2.0
tested with Ua Expert against standard and ref server

* Handle special case correctly, when zero bytes are received its ok, or BadTimeout will occur

* simplify connect, reduce DiscoverEndpoint calls
2017-09-15 09:37:32 +02:00
Erich Barnstedt e6f0ca9420 Upgrade to VS2017/.Net1.1 2017-06-09 17:50:23 +02:00
Marc Schier 2af2a4dd75 Add visual studio 2017 solution file to allow building .net Standard … (#150)
* Add visual studio 2017 solution file to allow building .net Standard stack and console samples

* Enable VS 2015 when VS 2017 is installed

* Update readme
2017-03-23 11:17:39 +01:00