-
Notifications
You must be signed in to change notification settings - Fork 641
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
changed dotnet new
example
#9309
Conversation
[ReleasePrep][2022.11.09]RI of dev into main
@baronfel fyi |
Thanks for the contribution, @vlada-shubina! I'm curious about the timing of this change, i.e. when should it go live on NuGet.org. Should it wait until a certain % of users move to .NET 7? Or do you think we should just go for it since .NET 7 is GA'd? What is the behavior if you use the new syntax on the old CLI or the old syntax on the new CLI? |
new syntax doesn't work in previous versions
aka.ms/dotnet-new leads to https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-new which explains new syntax almost on top. @baronfel do you know the adoption of .NET 7? when do you think we should go for the change? |
I spoke with @baronfel offline. Let's proceed with this chance given it is the new syntax, it's GA'd, and folks are actively adoption .NET 7. |
@vlada-shubina, thanks again for pushing this. I'll run the change through the CI and get the verification and deployment process rolling. |
FYI I changed the base branch to |
Merged to |
Starting .NET 7.0,
dotnet new --install
becamedotnet new install
.https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-new-install
Therefore changed syntax in example