You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Run the unit tests in a specific framework (verify that the library works in that framework)
150
164
- name: Run Tests
151
-
run: make test-fw fw=${{ matrix.framework }}
165
+
run: make unit-test FW=${{ matrix.framework }}
166
+
167
+
# .NET Standard notes:
168
+
# - NET Standard 2.0 is compatible with minimum .NET Framework 4.6.1: https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0
169
+
# - GitHub's Windows 2022 runner only supports minimum .NET Framework 4.7.2 anyway: https://github.com/actions/virtual-environments/issues/5055#issuecomment-1040757930
170
+
# - .NET Standard is not a framework, but a set of shared APIs between the old .NET Framework and new .NET/.NET Core
171
+
# - `EasyPost` targets .NET Standard 2.0, meaning it is compatible with specific versions of both .NET and .NET Framework: https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0
172
+
# - When you want to actually run code, however, you can't run it in .NET Standard. You have to run it in either .NET or .NET Framework: https://stackoverflow.com/a/48885500/13343799
173
+
# - So, while `EasyPost` targets .NET Standard 2.0, `EasyPost.Compatibility.NetStandard`, the code we're actually executing, targets .NET Framework 4.7.2
174
+
# - By extension, this is ensuring we are testing that the `EasyPost` source code can run in a .NET Framework environment
175
+
176
+
NetStandard_Compatibility_Tests:
177
+
# Need windows-2022 for .NET Framework 4.7.2 support
178
+
runs-on: windows-2022
179
+
steps:
180
+
- uses: actions/checkout@v5
181
+
with:
182
+
submodules: true
183
+
184
+
- name: Install .NET SDK
185
+
uses: actions/setup-dotnet@v5
186
+
id: setupid
187
+
with:
188
+
dotnet-version: 10.x.x
189
+
190
+
- name: Specify .NET SDK version to use since GitHub runners have multiple installed
# - NET Standard 2.0 is compatible with minimum .NET Framework 4.6.1: https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0
218
-
# - NET Framework 4.6.1 is EOL after April 26, 2022, due to its security concerns (was affected by the SHA-1 crack): https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-framework
219
-
# - GitHub's Windows 2022 runner only supports minimum .NET Framework 4.6.2 anyway: https://github.com/actions/virtual-environments/issues/5055#issuecomment-1040757930
220
-
# - .NET Standard is not a framework, but a set of shared APIs between the old .NET Framework and new .NET/.NET Core
221
-
# - `EasyVCR` targets .NET Standard 2.0, meaning it is compatible with specific versions of both .NET and .NET Framework: https://docs.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0
222
-
# - When you want to actually run code, however, you can't run it in .NET Standard. You have to run it in either .NET or .NET Framework: https://stackoverflow.com/a/48885500/13343799
223
-
# - So, while `EasyVCR` targets .NET Standard 2.0, `EasyVCR.Tests`, the code we're actually executing, targets .NET Framework 4.6.2
224
-
# - By extension, this is ensuring we are testing that the `EasyVCR` source code can run in a .NET Framework environment
0 commit comments