fix#940 and #975
- add namespace qualifier to complex type name
- improve handling of known subtypes
- fix Pss detection on .Net 462
- stronger check of valid DataTypeDefinition for servers which expose invalid structure (nodejs)
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 a few more dependent complex types for testing
- fix UI issue which prevents dialogs from showing data
* workaround for dialogs with imagestream, always throwing exceptions
* rebuild with v1.04 modelcompiler
* Fixes#709 - Allow HTTPS clients to send the certificate for servers that require TLS client authentication
* Fixes#692 - HTTPS Server listener - Use the first configured policy for HTTPS
* 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.
* fix windows form apps, when icon on the taskbar disappears but is still running
* use exceptiondlg where it was missing
* change GetAssemblyTimestamp, pe header is not containing a timestamp in .net core assemblies
* project fix
* resolve a circular dependency with opc.ua.sample
* fix dependency on HeaderBranding
* Stack updates for GDS server, to handle app cert signing and crl creation for CA
* GDS server / client fixes.
Supports signing of certs, app registration/unregistration, cert revocation
Build fails until sql db files are manually created
RegisterServer2() is called as first option for LDS registration of the server.
The ClientControls was extended to use FindServersonNetwork() into the LDS-ME for discovering the OPC UA Servers announcing themselves using Bonjour services.
-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
2. Added generate cert script to project files.
3. Made "\\" platform independent, even for .Net4 samples (apart from GDS samples).
4. Fixed cert validation popups (yes/no was reversed!).
5. Got GDS server and client samples running (no connection yet).
6. Fixed configuration and popups in GDS client.
2. Removed "netcoreapp1.0" from project.json as it is not required.
3. Updated generated OPC type classes with latest definitions.
4. Added session-less request validation.
5.Added small helper method in certificate store ID class.
6. Added OAuth2 credentials.
7. Brought original user identities back in (username, cert, certIDs) and added JWTs.
2. Removed client cert validation from HTTPS client and server as this is not supported on all platforms, e.g. .Net4.6.
3. Reverted back to XmlDocument from XDocument as this is now supported via a NuGet package on UWP and XDocument is not supported on .Net4.6.
4. Baseline .Net4.6 samples and assoc. controls project check-in, not working yet.
5. Moved UWP client controls from SDK to Samples directly.
Martin Regen