Improve text for OpenSsl primitives when OpenSSL is not available #89046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using any of the *OpenSsl primitives on macOS, the current exception text is somewhat confusing. Before, it would be
After this change, it will be:
This only affects using the *OpenSsl primitives on macOS since it is the only platform where we "support" OpenSSL but don't outright require it. Windows, Android etc. will continue to use the OpenSsl.NotSupported.cs in their complication targets:
runtime/src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/OpenSsl.NotSupported.cs
Lines 74 to 77 in ae4d698
So those platforms will continue to receive the former exception message.
cc @mvoss84
Contributes to #89006