-
Notifications
You must be signed in to change notification settings - Fork 5.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
Why? #26548
Comments
@Korporal technically 6.0 hasn't shipped yet, it's still in the preview... Presumably this will be simpler once we ship but let's see if we can get clarification on that. cc: @richlander @terrajobst |
My understanding is that we don't plan to make changes for 6.0 RTW. However, we're going to collect more user data as more and more people will move to .NET 6. Yes, we hear some strong feedback but to be frank, it's unclear whether it's a very loud minority or a problem for a large chunk of our user base. Right, the belief on our side is that the feedback is coming from a minority, hence no plan to make changes for RTW. @KathleenDollard and/or @DamianEdwards should have the latest here. |
See #26313, where you can vote on the new template code. Closing this issue in favor of that one. |
Frankly this is so contrived! Having to create a project as .Net 5 then hand edit the project's target to be .Net 6 as the way to get a .Net 6 console app with the usual class etc is just bizarre.
This really should be an opt-in, just add a check box on the final page of the project create operation "Use new console style" or something and make that checkbox only visible for .Net 6 or later targets.
Defaulting to the minimal form this way suggest a rushed decision, just not thought through very well, why adding a checkbox for this was not the obvious choice is a mystery!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: