DataProtection/test/Microsoft.AspNetCore.DataPr.../XmlEncryption
Nate McMaster b706a75e03 Target .NET Standard 2.0
This retargets all data protection libraries to ns2.0. This means .NET
Framework applications will need to upgrade to .NET Framework 4.6.1.
This upgrade makes available API to .NET Core that was previously only
available on .NET Framework, such as encrypting keys at rest with
certificates.

New API for .NET Core users:
- IDataProtectionBuilder.ProtectKeysWithCertificate(string thumbprint)
- CertificateXmlEncryptor
- ICertificateResolver
- DataProtectionProvider
  - .Create(string applicationName, X509Certificate2 certificate)
  - .Create(DirectoryInfo keyDirectory, X509Certificate2 certificate)
  - .Create(DirectoryInfo keyDirectory, Action<IDataProtectionBuilder>
  setupAction, X509Certificate2 certificate

Other minor changes in this commit:
- Fixed samples that were using obsolete logging API
- Remove calls to api-sets, instead using kernel32. .NET Core 2.0 no
longer requires using api-sets as Nano Server now forwards kernel32
calls
- Made minor improvements to the TypeForwardingActivator
- Remove dead code an unused api baselines
- Enable more tests on macOS/Linux that previously only ran on Windows
2017-05-24 09:47:10 -07:00
..
CertificateXmlEncryptionTests.cs Target .NET Standard 2.0 2017-05-24 09:47:10 -07:00
DpapiNGXmlEncryptionTests.cs [Fixes #134] Refactored DI support 2017-03-14 19:58:46 -07:00
DpapiXmlEncryptionTests.cs Target .NET Standard 2.0 2017-05-24 09:47:10 -07:00
NullXmlEncryptionTests.cs Rename AspNet 5 file contents. 2016-01-22 12:32:33 -08:00
XmlEncryptionExtensionsTests.cs [Fixes #134] Refactored DI support 2017-03-14 19:58:46 -07:00