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.
* fix schema validator and dictionary loader (only binary scheme)
# include some .bsd files for validation
* add check for some configuration fields, to return a meaningful error.
* Update for 1.04 attributes in ClientSession.ReadNode()
* Fix in ClientSession.ReadNode()
* Updates for 1.04 Attributes in server.
* Discard inner value for attributes with bad status codes in ClientSession.ReadNode().
* Remove unused attribute from AttributeWriteMask
Fixed wrong null checks for Notification message in GetServiceResult(IEncodeable notification) and GetServiceResult(IEncodeable notification, int index)
* add the Aes128 and Aes256 profiles
* Aes profies were tested on IoP workshop against Ascolab, Softing, Matrikon, Milo, ProSys and others
* Pss padding is not supported on all platforms, so autodetect if it is supported and filter out Aes256 if not
* not a breaking change: not specifying the SecurityProfileUri in the config xml will automatically add all supported profiles but not deprecated profiles (e.g. Basic256Sha256, Aes128, Aes256). Aes256 is only added if the platform supports Pss padding. This will simplify the maintenance of config xml, since automatically all supported and secure profiles are exposed.
- all changes for cloud based GDS
- build version of .net standard libs is now set in version.props, it may require updates for the official builds.
- add new stuff for v1.04 nodeset, e.g. QueryApplications Api
- gds.client/gds.server common dll changes to support a cloud based GDS.
* Fix for Mantis #4231. Refuse to use untrusted certificates to encrypt user identity tokens sent to servers.
* Deprecated security policies removed from default server config.xml files.
The AddRefrences method exists in similar versions in several of the sample node manager classes. The method loops through a list of (external) references and adds them to the designated objects. When obtaining node handles it also checks that the node is valid in the current context. The problem was that it skipped the rest of the nodes in the list as soon as it found one node that wass not valid. This change ensures that all nodes in the references list are processed.
The AddRefrences method loops through a list of (external) references and adds them to the designated objects. When obtaining node handles it also checks that the node belongs to one of the namspaces for the current node manager. The problem was that it skipped the rest of the nodes in the list as soon as it found one node that did not belong to the currennt node manager.
- Fix the NO_HTTPS build to reduce publish size if HTTPS is not needed
e.g. `dotnet build /p:NoHttps=true`
- Limit language Version to C#6 for VS 2015 compat
- add travis & appveyor cases for nohttps build
- enable GDS Https transport
- update nuspec
- remove dependency on System.Private.ServiceModel, it should not be used directly
- remove packages.config, VS2017 doesn't need it
- use ref to .Net instead of nuget to reduce number of packages used
Martin Regen