- this is part of an effort to deprecate netstandard1.3 support (#761)
- as a result Windows 10 minimal version is now >= 16299 (Fall Creators Update 2017)
* 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.
* 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
- 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. 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