Expand framework support and COM ABI coverage

Target .NET 8, 9, 10, Framework 4.7.2, and Framework 4.8. Rename samples to stable Core and Framework names. Add raw-vtable COM tests for x64, x86, and ARM64, and require the Azure architecture matrix before packaging.
This commit is contained in:
Ryan Newington
2026-08-28 11:22:53 +10:00
parent be65cbaa93
commit 43af44f87f
52 changed files with 1116 additions and 128 deletions
+3 -3
View File
@@ -9,7 +9,7 @@ A library for creating secure Windows Credential Providers in .NET, without the
The Lithnet Credential Provider for Windows provides an easy way to create a credential provider, without having to implement the COM components. The COM components are still there, but abstracted away into a fully managed implementation.
## Getting started
* Create a new Class Library project. You can use .NET Framework 4.6.1 or higher, or you can use .NET 6.0 or higher) to create your provider. You must build as either an x64 or x86 binary. You cannot use AnyCPU.
* Create a new Class Library project. You can use .NET Framework 4.7.2 or later, or .NET 8.0, 9.0, or 10.0. You must build an x64 or x86 binary. You cannot use AnyCPU.
* Install the package from nuget `Install-Package Lithnet.CredentialProvider`
* Modify the `csproj` file and set `RegisterForComInterop` to `false`
@@ -21,11 +21,11 @@ The Lithnet Credential Provider for Windows provides an easy way to create a cre
</PropertyGroup>
```
* If you are using .NET 6 or higher, you must also set `EnableComHosting` to `true`
* If you are using .NET 8.0, 9.0, or 10.0, you must also set `EnableComHosting` to `true`.
```xml
<PropertyGroup>
<TargetFramework>net6.0-windows</TargetFramework>
<TargetFramework>net8.0-windows</TargetFramework>
<RegisterForComInterop>false</RegisterForComInterop>
<Platform>x64</Platform>
<EnableComHosting>true</EnableComHosting>