-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlatformNotSupportedException: 'CspParameters' issues when running tests on Linux #6
Comments
Hi, For today, For now, you need to use As to the legacy projects, I want to keep them for now until this PR is fully merged since it minimizes conflicts when updating from the source branch. |
Thanks for the background, can appreciate those pain points. Till then, how do we test this on linux? |
For now, the build and test needs to be on Windows, but the resulting library will work anywhere. |
I needed to verify that assumption. Turns out there indeed are test issues on *nix but thankfully nothing too bad. I got Here is the console log - since the tests have parameterized input, the exact failures aren't clear without diving a bit deeper On Windows 784 of 788 test pass, on macOS 783 (1 failure) of 788. No idea about the 4 in between (ignored?)
|
FYI, tried this on Ubuntu 16.04 too. Test failure as follows - assumptions about CAPI being broken x-platform. You can try using Ubuntu on Windows 10 (via WSL)
|
Haven't had a chance to look at the interop issues, but |
Hi, Do you know of any workaround I can use to create a |
I found a workaround: Instead of calling var rsa = DotNetUtilities.ToRSA(keyParameters); I'm using var rsa = RSA.Create(DotNetUtilities.ToRSAParameters(keyParameters)); and it works. I'd like to replace this method: bc-csharp/crypto/src/security/DotNetUtilities.cs Lines 242 to 249 in 163f40d
with private static RSA CreateRSAProvider(RSAParameters rp) => RSA.Create(rp); However, I don't know the implications of doing so and if that can break something else on some platform. |
This repo is mirror of the main repo with the only changes being to enable the portable build. For a functional change like you're proposing, I recommend creating an issue here: https://github.com/bcgit/bc-csharp/issues |
Closing due to age. |
Failure: Basic CLI commands like
dotnet test
ordotnet build
don't seem to work.Expectation:
dotnet build
should build the project(s) based on the platform it's invoked on and folder it's invoked indotnet test
should run the test project (nunit 3.x tests should be automatically discovered and executed viaMicrosoft.NET.Test.Sdk
- this seems to be already in place).Related cleanup suggestions
csproj
files (crypto\crypto.csproj
andcrypto-test\crypto-test.csproj
) that throw off the modern dotnet CLIcrypto\test\crypto.test.csproj
and acrypto-test\crypto.test.csproj
project adding to confusion.Log of
dotnet build
failingThe text was updated successfully, but these errors were encountered: