Recommend no System.Security.Cryptography.CryptoAPITransform and RijndaelManagedTransform about standard HOT 5 CLOSED

@steveharter while I can understand that we might not want these concrete types is there actually any bad things that come from keeping them? I don't think just the fact that someone might case to them is a good enough reason to exclude them.

from standard.

The types will not be usable (PNSE on every member) and not created by corefx nor by anyone else since the ctor is internal. The class should not have been public to begin with. So if we keep them it would be "just for contract reasons" meaning compile works but nothing at run-time. Isn't it better to change any consuming code at compile-time vs later at run-time when the usage is destined to fail (at least on corefx)?

from standard.

@weshaggard I'm not sure that shipping useless types is an easily defensible position. That the types can only be successfully used on Windows may be an argument to include them ... but it is not a strong one. Although perhaps including them and marking them deprecated them might be an interesting choice.

from standard.

@weshaggard I'm not sure that shipping useless types is an easily defensible position.

The principals for .NET Standard is to include everything in the interesction unless we have a reason not to (see https://github.com/dotnet/standard/tree/master/docs/netstandard-20). There are lots of things in netstandard that might be considered useless but it really depends on your prospective.

For these particular types given they are leaf node types which don't have any real usage in our data and are windows specific I'm OK excluding them. I will exclude them.

@terrajobst any thoughts?

from standard.

Both types have extremely low usage. I'd be fine with removing them.

from standard.