consoleasync yields lowercase only project reference in the solution file
Type of issue
Code doesn't work
Description
On Linux (LMDE 6), when using the template "consoleasync" to create the "MyProject" project, the template yields a solution file with a lowercase project reference, i.e. "myproject" and the dotnet restore command fails. Both the project and solution files have the expected case in their filenames though, i.e., "MyProject.sln" and "MyProject.csproj"
` File, Format Version 12.00
Visual Studio Version 17
VisualStudioVersion = 17.5.002.0 MinimumVisualStudioVersion = 10.0.40219.1 Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "myproject", "myproject.csproj", "{7E7006D5-2A3E-4F1A-B087-2F131B7542E8}" EndProject Global GlobalSection(SolutionConfigurationPlatforms) = preSolution Debug|Any CPU = Debug|Any CPU Release|Any CPU = Release|Any CPU EndGlobalSection GlobalSection(ProjectConfigurationPlatforms) = postSolution {7E7006D5-2A3E-4F1A-B087-2F131B7542E8}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {7E7006D5-2A3E-4F1A-B087-2F131B7542E8}.Debug|Any CPU.Build.0 = Debug|Any CPU {7E7006D5-2A3E-4F1A-B087-2F131B7542E8}.Release|Any CPU.ActiveCfg = Release|Any CPU {7E7006D5-2A3E-4F1A-B087-2F131B7542E8}.Release|Any CPU.Build.0 = Release|Any CPU EndGlobalSection GlobalSection(SolutionProperties) = preSolution HideSolutionNode = FALSE EndGlobalSection GlobalSection(ExtensibilityGlobals) = postSolution SolutionGuid = {9A37600B-3443-4744-85E0-4A1BCFBF191F} EndGlobalSection EndGlobal ` If I change the project reference line to ".."MyProject", "MyProject.csproj"..", the project compiles and runs as expected.
Page URL
https://learn.microsoft.com/en-us/dotnet/core/tutorials/cli-templates-create-project-template?source=recommendations
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/tutorials/cli-templates-create-project-template.md
Document Version Independent Id
77b25381-6e0f-949f-5f96-b83e9b61e9fc
Article author
@adegeo
Metadata
- ID: 097102bb-f6d9-c469-5556-ae1f16fdc4fe
- Service: dotnet-fundamentals
Thank you for reporting this. I put this on next month's sprint to investigate.
Sorry for the delay. None of the commands used in the tutorial to create the template will generate a SLN file. You must have opened up the project in an IDE that generated a solution file and it accidentally got ingested into the template. I'm going to close this issue as I don't think there is actually anything to correct in the article.