Upgraded all project from .NET 4.6 to .NET 4.6.2 that also .NET framework applications can use latest version of Kestrel
* Updated Kestrel to 2.2.0 (for Opc.Ua.Core)
* Simplified csproj (removed ItemGroup Condition="'$(TargetFramework)' == 'netstandard1.3'") because currently we don't build netstandard1.x anymore
* Removed Kestrel 1.1.3 code from Stack/Opc.Ua.Core/Stack/Https/HttpsListener.cs
* add conditions to Stack/Opc.Ua.Core/Stack/Https/HttpsTransportChannel.cs
* [HttpClientHandler.ServerCertificateCustomValidationCallback](https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.servercertificatecustomvalidationcallback?view=netcore-3.1&viewFallbackFrom=netframework-4.6.2) should not be available in .NET 4.6.X
* Updated travis.ci to use latest mono version (original version causes build errors)
* Added nuget reference .NET Standard Library to mono projects to be compatible with latest Kestrel version
Own Travis.ci and Azure Pipeline builds run sucessfully.
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.
* 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.
- best possible fix for #189 to reenable https servers
- `UA Sample Client` and `UA Sample Server` expose https server. libuv.dll is by default for x64. Change
```
<PropertyGroup>
<RuntimeIdentifier>win7-x64</RuntimeIdentifier>
<BaseNuGetRuntimeIdentifier>win7-x64</BaseNuGetRuntimeIdentifier>
</PropertyGroup>
```
to win7-x86 if required.
- fix exception in https client when setting the Timeout
- fix travis build script for linux. kestrel server on ubuntu doesn't respond on ipv6Any ipaddress.
- fix a timing problem in the travis script.
* Fixes for https client and server (#38)
HTTPS server fixes:
- Kestrel 2.0 in netcoreapp 2.0 server samples: only responds to some clients, not to UA samples at all. Fix configuration (listen to all ip addresses)
HTTPS client fixes:
- bug: client gets stuck if subscription is active by nesting too many calls (use async callback)
- https client needs server cert in a trusted store or it refuses connection (auto accept server certs, but fix is not supported on all platforms, e.g. UWP apps still require a cert in the trusted store)
- runtime issues with .Net 4.6. apps (cannot find diagnostics dll) --> workaround is to manually add nuget package of System.Net.http 4.3.3
- Add https connection to travis test script (only .Net Core)
* fix shell script exe
* also listen on ipv6 port
* do not use auto validation on OSX
Causing problems when CRLF conversion is enabled and when diffing in PR.
* SampleServer.cs to UTF-8
* SampleServer.SampleModel.cs to UTF-8
* SampleServer.UserAuthentication.cs to UTF-8
* remove .cs extension from forced text attribute
* DataComparer.cs to UTF-8
* Program.cs to UTF-8
-delete the obsolete uanodes/txt files in project folders
note: clean build required, make sure all dll are updated in bin folders or resources in dll may not be found
- certs were not created on Linux w. Openssl if a passcode was missing from the pkcs12 store
- stabilize the creation on windows where UWP is picky about the storage keys to use
- CR feedback
- create self signed cert on first start (kudos to bouncy castle)
- fix path handling in many areas,
- ./ or ../ is treated as rooted dir
- special %LocalFolder% for UWP apps to allow to write certs in app temp storage
- all batch helpers to create certs removed
Alexander Köpke