Lab 6 - dotnet new command needs to be updated
See original GitHub issueModule: AZ-204
Lab/Demo: 06
Task: 01 (Exercise: 02)
Step: 03
With the availability of .NET 6 - the following command produces the boilerplate code without Program.cs and Startup.cs
Most of the lab is around .Net Core 3.1 and there is also a reference to Startup.cs
It would be ideal to update the command and add the --framework parameter that would generate the code that is targetted for v3.1
dotnet new mvc --framework .netcoreapp3.1 --auth SingleOrg --client-id <application_ID> --tenant-id <tenant_ID> --domain <domain_Name>
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (3 by maintainers)
Top Results From Across the Web
dotnet new <TEMPLATE> - .NET CLI
The dotnet new command creates new .NET projects based ... To use --update-check , use the update subcommand with the --check-only option.
Read more >How to make dotnet core select a lower version?
If you want to change this version to some other version installed in the system, type the following in the command prompt. dotnet...
Read more >dotnet new update - .NET CLI
The dotnet new update command with --check-only option checks for available updates for installed template packages without applying them. Note.
Read more >Lab 06: Authenticate by using OpenID Connect, MSAL, and ...
In the Visual Studio Code window, from its top menu bar, go to Terminal menu and select New Terminal. In the Terminal panel,...
Read more >Module Three - .NET Workloads on AWS App Runner
In this step, you'll use the dotnet new command to create a Web API project, and update its code to retrieve data from...
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 Free
Top 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

Then wouldn’t the ideal solution be to update the lab environments to the latest LTS version? I do realize this may take a while to update all of the exercises, but I’m gonna assume we don’t just want to support 3.1 forever.
I’d be willing to take some of the work upon myself, I’m still learning Azure myself, so some more repetition definitely won’t hurt 😃.
Depends on what .net core versions are installed in the lab environment. In actual scenarios, the users might have more than one version installed in that instance dotnet new command would use the latest version. The latest dotnet version would not generate Startup.cs file.