With #55690 merged, the implementations of the S.S.Cryptography assemblies have been consolidated in to a single in-box assembly, where possible.
The unit tests for these are still in their separate projects however, such as S.S.C.Algorithms, S.S.C.Cng, etc.
This issue is to track consolidating them under System.Security.Cryptography. Note that this is not as simple as moving the files and adjusting namespaces. We made heavy use of partials to test different implementations of algorithms (internal vs public CNG for example). The partial approach won't work. The current solution is to refactor to a "driver" base type and test each implementation as a derived type.
With #55690 merged, the implementations of the S.S.Cryptography assemblies have been consolidated in to a single in-box assembly, where possible.
The unit tests for these are still in their separate projects however, such as S.S.C.Algorithms, S.S.C.Cng, etc.
This issue is to track consolidating them under System.Security.Cryptography. Note that this is not as simple as moving the files and adjusting namespaces. We made heavy use of partials to test different implementations of algorithms (internal vs public CNG for example). The partial approach won't work. The current solution is to refactor to a "driver" base type and test each implementation as a derived type.