Comments (6)
A bunch of the missing APIs (like all the Marshal.* ones) were added recently and will show up in the latest Xamarin Cycle8 build.
For the other cases, I agree we should take a look if it makes sense to expose/fix them in Xamarin. (Marek and me are both on vacation right now, so expect a bit of delay 😄 )
from standard.
Maybe this isn't the right place, but for System.Security.Cryptography, here's my take:
Definitely cut:
- MembersMustExist : Member 'System.Security.Cryptography.Rfc2898DeriveBytes.CryptDeriveKey(System.String, System.String, System.Int32, System.Byte[])' does not exist in the implementation but it does exist in the contract.
- We copied this from PasswordDeriveBytes so we could cut it while keeping the method. Then we killed the method because it can't work on UWP or Unix. Since the method still can't work on UWP or Unix, cut it. (It also didn't belong on PasswordDeriveBytes, it just got dropped in there for some reason).
Happy to cut (catalog says there's no usage):
- MembersMustExist : Member 'System.Security.Cryptography.CryptoConfig.AddAlgorithm(System.Type, System.String[])' does not exist in the implementation but it does exist in the contract.
- Edit: This one has 0.1% usage in the catalog, but I'm still happy to cut it.
- MembersMustExist : Member 'System.Security.Cryptography.CryptoConfig.AddOID(System.String, System.String[])' does not exist in the implementation but it does exist in the contract.
- MembersMustExist : Member 'System.Security.Cryptography.RC2CryptoServiceProvider.UseSalt.get()' does not exist in the implementation but it does exist in the contract.
- MembersMustExist : Member 'System.Security.Cryptography.RC2CryptoServiceProvider.UseSalt.set(System.Boolean)' does not exist in the implementation but it does exist in the contract.
- MembersMustExist : Member 'System.Security.Cryptography.RNGCryptoServiceProvider..ctor(System.Byte[])' does not exist in the implementation but it does exist in the contract.
- MembersMustExist : Member 'System.Security.Cryptography.RNGCryptoServiceProvider..ctor(System.Security.Cryptography.CspParameters)' does not exist in the implementation but it does exist in the contract.
- MembersMustExist : Member 'System.Security.Cryptography.RNGCryptoServiceProvider..ctor(System.String)' does not exist in the implementation but it does exist in the contract.
(Everything else is about sealed v virtual, serialization, or MarshalByRefObject)
from standard.
Thanks @bartonjs I took care of those with 6d04955.
@marek-safar @akoeplinger I've been pruning down the compat issues listed at https://github.com/dotnet/standard/blob/master/netstandard/src/ApiCompatBaseline.xamarin.ios.txt and I'm still working through it but I'd be interested in your guys input on some of them.
- MarshalByRefObject base class removed from a number of classes.
- AccessControl APIs it looks like you have a number of them but you also have a number of them removed. I'm going to dig into that entire API surface soon and I'm curious if you can help me understand the logic you guys were using there.
- Removal of Component as a base class. It looks like you guys remove it from FileSystemWatcher but kept it for things like Process and Timer. Any insights to the logic would be helpful. I'm tempted to remove Component base type from everything that isn't under ComponentModel directly.
There will be other questions those are some buckets I would like to better understand. Also it would be good to understand which set of APIs you guys think you will be adding.
from standard.
- MarshalByRefObject: XI/XA don't support remoting hence the base type is not useful
- AccessControl: I think the logic comes from SilverLight but I don't think such APIs are used much in wild if at all.
- Component: We've added FileSystemWatcher only recently as empty skeleton (throws NIE) so not much time was spent on that type and we always start with smaller dependencies and add more later than the other way. Removing Component from other types would be nice but it's a breaking change.
from standard.
Thanks @marek-safar.
Similar to removing Component removing MarshalByRefObject is a breaking change. I realize we aren't going to support remoting but having the that type doesn't actually cause much in terms of APIs (704c6c5) and we can just make some methods on MarshalByRefObject throw not supported.
from standard.
It's breaking change against .NET FX but not against XI/XA which I was referring to. As you wrote we could add MarshalByRefObject quite easily (throw PNS everywhere) but not sure how useful it'd be.
from standard.
Related Issues (20)
- Build issues when referencing project that targets multiple frameworks C# WPF HOT 1
- Questions about tagging within this repository / future versions HOT 1
- System.Drawing.Printing.PrinterSettings slow HOT 1
- Support with Universal Windows Platform HOT 2
- How to build .NET Standard based library for ARM architecture HOT 6
- Update docs to reflect the status of .NET Standard in 2020 HOT 2
- [BUG] [UWP] GetManifestResourceInfo doesn't work on UWP HOT 3
- Value Tuple Could not load file or assembly 'System.ValueTuple, Version=4.0.1.0, HOT 1
- mono and .NET5+ HOT 8
- Security Vulnerability due to System.Text.RegularExpressions HOT 4
- Issue with resolving between .NET Standard 2.0 and .NET Standard 2.1 HOT 3
- Class ValueTask has different definitions between .Net Standard 2.1 and .Net 5 HOT 1
- Strong name signature not valid HOT 5
- Assembly version for DispatchProxy shim is too low resulting in duplicate types for DispatchProxy HOT 10
- linq using GetValueOrDefault in Where clause problem HOT 3
- DbCommand.ExecuteReaderAsync throws TaskCanceledException with wrong CancellationToken HOT 2
- [Feature Request] Allow Static Method In Interface HOT 3
- [question] Will Garbage Collector Collect Memebers, When Object Is Casted To Parent Type, That Is Now Inaccessible On The Type Of Reference? HOT 2
- [Feature Request] Support for MultiSet & MultiMap in System.Collections.Generic HOT 3
- Support of 'IAsyncComparer' for Linq operations. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standard.