Improve RandomNumberGenerator documentation to prefer static APIs #8023
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.
Summary
The
RandomNumberGenerator
class is currently documented as a base class which other random number generators should derive from, and that callers are expected to use a derived class.We've de-emphasized using derived classes for
RandomNumberGenerator
, going so far as to obsolete the only in-box derived type,RNGCryptoServiceProvider
.These changes attempt to steer people toward using the new static APIs, instead of
Create
or derived types.