API Compat: the reference assembly is allowed to have more overrides than the implementation
See original GitHub issueSuppos a reference assembly includes an overide that the implementation doesn’t have. Then, API Compat creates an error like this:
MembersMustExist : Member 'System.IO.FileStream.Read(System.Span<System.Byte>)' does not exist in the implementation but it does exist in the contract.
However, IL was designed to handle cases like this. In fact, we may want to always have all the overrides to bad base
calls in C# should we add an overide later.
See this thread for more context.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Net picking wrong referenced assembly version
I just copied an existing project to a brand new machine to start developing on it and have run into a problem with...
Read more >[CA1416] Allow child APIs attribute override assembly ...
This is an expected scenario by design, child APIs should not extend parent support. SupportedOSPlatform illustrates that the API/assembly only ...
Read more >MSB3277: Found conflicts between different versions of ' ...
This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the...
Read more >Assembly definitions
In the General section, enable the Override References option. The Assembly References section of the Inspector becomes available when Override References is ...
Read more >Customizing resolution of a dependency directly
The feature currently offers the ability to change the group, name and/or version of a requested dependency, allowing a dependency to be substituted...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also, should we archive dotnet/build tools now?
Yeah, this is an ask to relax a rule in APICompat. Any chance we can have labels to triage this sort of thing @markwilkie?