-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dotnet-sdk-10.0.100-preview.1.25103.13] Some apps retarget failed with CS0121 and CS0428 System.Linq errors #112462
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
1 similar comment
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@marcpopMSFT Could you please have a look at this bug and help triage it? Thanks! |
@jcouv Could you please take a look at this issue and confirm whether it is a blocker for .NET 10.0 Preview1 validation? Thanks |
This doesn't look like a compiler issue. The extension method is defined in two assemblies given to the compiler (details below the fold). If you remove the reference to First one: Second one: Here are the two references given to the compiler: |
Moving to runtime as this is caused by new APIs. Will let them decide how to proceed here. |
Tagging subscribers to this area: @dotnet/area-system-linq |
This is something that got discussed here: #79782 (comment) TL;DR we need a deprecation plan and document relevant workaround in cases where there are conflicts due to transitive dependencies. |
@Junjun-zhao Does the workaround described here address you immediate issue? |
@eiriktsarpalis We have tried the workaround, two applications have worked with it. The third one is still in progress and I will update the result once it is completed. There is another application also encountered CS0121 issue, could you please help look at this issue and help move to the right team if it is not. Thank you very much. |
@eiriktsarpalis Besides the deprecation plan, will you be going to create a breaking change document for this change? |
.NET adding APIs that conflict with third party packages is fairly common, it isn't something we consider a breaking change. We will make sure that the legacy System.Linq.Async package includes guidance for users looking to move away from it. |
Application Name: Smartstore, blog, nopCommerceNetCore
OS: Windows 10 22H2
CPU: X64
.NET Build Number: dotnet-sdk-10.0.100-preview.1.25103.13
App & Source Location checking at: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2379210
Github Link:
https://github.com/smartstore/Smartstore
https://github.com/sagebind/blog
https://github.com/nopSolutions/nopCommerce
Verify Scenarios:
1). Windows10 21h2 x64 + dotnet-sdk-8.0.405 + default target 8.0: Pass
2). Windows10 21h2 x64 + dotnet-sdk-9.0.102 + retarget 9.0: Pass
3). Windows10 21h2 x64 + dotnet-sdk-10.0.100-preview.1.25103.13 + default 8.0: Pass
4). Windows10 21h2 x64 + dotnet-sdk-10.0.100-preview.1.25103.13-win-x64 + retarget10.0: Fail
Description :
When retargeting Smartstore app to .NET 10, it is built failed with CS0212 and CS0428 errors:
Minimal Repro Steps:(Demo attached: AmbiguousCallDemo.zip)
Make sure the machine has dotnet-sdk-dotnet-sdk-10.0.100-preview.1.25103.13 installed.
Expected Result:
Build successful.
Actual Result:
Build Failed with below errors:
DotNet Info:
Findings:
After investigating, we found all the methods or properties thrown from errors come from
System.Linq.Async
nuget package.@dotnet-actwx-bot @dotnet/compat
The text was updated successfully, but these errors were encountered: