-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Compilation error #55855
Comments
after introduction of these functions to LINQ This is requires bump of expected version in global.json Closes #1334
Tagging subscribers to this area: @eiriktsarpalis Issue DetailsWhen on
|
What is Internal.CommandLine ? It seems like there are two equally valid extension methods, and so the compiler is telling you it doesn't know which to pick. That's by design. |
It is command line parser for crossgen2 tool and other tools. |
I update original issue with locations of the code which was breaking for me. |
Is this happens because of implicit namespace imports? |
Oh wow - https://docs.microsoft.com/en-us/dotnet/core/tutorials/top-level-templates#use-the-new-program-style For console applications, the following directives are implicitly included in every source file in the application: using System;
using System.Collections.Generic;
using System.Linq;
using System.Net.Http;
using System.Net.Http.Json; 🤮 Looks like the docs miss one very important piece of information: how do I tell MSBuild "HELL NO!" to this? |
Yes. I confirm that System.Linq added to There only 2 places in repo where
and
so I assume I should add |
Hm, that disables the support for I think we'll want |
You could also do |
Not a fan of that. dotnet/sdk#18825 is already discussing adding new additional usings that are going to cause more build breaks. E.g. the proposed System.Diagnostics addition is going to break the build for Chocolatey, Microsoft Terminal, azure pipelines agent and countless other projects. The discussion shouldn't really be about what other namespaces we add by default, but what namespaces should be removed from the defaults. The only ones that are maybe, maybe, okay are |
My suggestion was to show another way of solving the issue, and not discuss global usings in general. |
Understood - I was just trying to point out that solution wouldn't satisfy the "so that we never have to deal with that in our tools again" part. |
|
@kant2002 already has a pull request in flight: dotnet/docs#25232 |
When on
.NET SDK 6.0.100-preview.7.21359.1
This is code from here
runtime/src/coreclr/tools/Common/CommandLine/Enumerable.cs
Lines 21 to 29 in 6b6310b
and here
runtime/src/coreclr/tools/Common/CommandLine/Enumerable.cs
Lines 42 to 45 in 6b6310b
The text was updated successfully, but these errors were encountered: