'dotnet new sln' should create version 16 .sln files
See original GitHub issueExpected behavior
It’s now documented that Visual Studio 2019 version 16.4 or a later version is required to develop .NET Core applications.
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 16
VisualStudioVersion = 16.4.29519.181
MinimumVisualStudioVersion = 16.4.29519.181
Actual behavior
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 15
VisualStudioVersion = 15.0.26124.0
MinimumVisualStudioVersion = 15.0.26124.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:6 (2 by maintainers)
Top Results From Across the Web
'dotnet new sln' should create version 16 .sln files #4853
Expected behavior It's now documented that Visual Studio 2019 version 16.4 or a later version is required to develop .NET Core applications.
Read more >dotnet sln command - .NET CLI
The dotnet-sln command provides a convenient option to add, remove, and list projects in a solution file.
Read more >NET Core - When to use "dotnet new sln"
Is "dotnet new sln" a new command? Yes. In version 1.0.1 of the dotnet command line interface, there is a dotnet new sln...
Read more >Project Solution (.sln) file - Visual Studio (Windows)
A solution is a structure for organizing projects in Visual Studio. The solution maintains the state information for projects in two files: .sln...
Read more >Visual Studio 2019 is still changing version in solution file ...
However, with same version number in my existing solution file, Visual Studio 2019 will change it Version 16 one after rebuild on solution....
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
And while you’re at it, change it to an XML style like the SDK style csproj.
This was already fixed in .NET 6, moving to version 17 is discussed in https://github.com/dotnet/templating/issues/4852