From ccf5752474c241cc786253203901371520bf9ee5 Mon Sep 17 00:00:00 2001
From: Jeffrey Stedfast <jestedfa@microsoft.com>
Date: Fri, 20 Dec 2024 10:51:16 -0500
Subject: [PATCH] Added netstandard2.1 to the build targets

There are a number of APIs in BouncyCastle that are conditionally enabled
(such as APIs that make use of `ReadOnlySpan<T>`) when
`#if NETSTANDARD2_1_OR_GREATER` evaluates to `true`.

This causes issues if any library that references BouncyCastle targets netstandard2.1
(and would therefore build against the netstandard2.0 version of BC) is, itself,
referenced by an app (or other library) that targets net6.0+, resulting an a
"missing implementation" error.

Fixes issue #447 (at least in a practical sense)
---
 crypto/src/BouncyCastle.Crypto.csproj | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crypto/src/BouncyCastle.Crypto.csproj b/crypto/src/BouncyCastle.Crypto.csproj
index c8049ad86..50a2aac7c 100644
--- a/crypto/src/BouncyCastle.Crypto.csproj
+++ b/crypto/src/BouncyCastle.Crypto.csproj
@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <TargetFrameworks>net6.0;netstandard2.0;net461</TargetFrameworks>
+    <TargetFrameworks>net8.0;net6.0;netstandard2.0;netstandard2.1;net461</TargetFrameworks>
     <RootNamespace>Org.BouncyCastle</RootNamespace>
     <AssemblyOriginatorKeyFile>..\..\BouncyCastle.NET.snk</AssemblyOriginatorKeyFile>
     <SignAssembly>true</SignAssembly>