Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article applies to: ✔️ .NET 6 SDK and later versions
Name
dotnet new - Creates a new project, configuration file, or solution based on the specified template.
Synopsis
dotnet new [--dry-run] [--force] [-lang|--language {"C#"|"F#"|VB}]
[-n|--name ] [-f|--framework ] [--no-update-check]
[-o|--output ] [--project ]
[-d|--diagnostics] [--verbosity ] [Template options]
dotnet new -h|--help
Description
The dotnet new command creates a .NET project or other artifacts based on a template.
The command calls the template engine to create the artifacts on disk based on the specified template and options.
Note
Starting with the .NET 7 SDK, the dotnet new syntax has changed:
- The
--list,--search,--install, and--uninstalloptions becamelist,search,install, anduninstallsubcommands. - The
--update-applyoption became theupdatesubcommand. - To use
--update-check, use theupdatesubcommand with the--check-onlyoption.
Other options that were available before are still available to use with their respective subcommands.
Separate help for each subcommand is available via the -h or --help option: dotnet new lists all supported options for the subcommand.
Additionally, tab completion is now available for dotnet new. It supports completion for installed template names and for the options a selected template provides.
To activate tab completion for the .NET SDK, see Enable tab completion.
Tab completion
Starting with .NET SDK 7.0.100, tab completion is available for dotnet new. It supports completion for installed template names, as well as completion for the options a selected template provides.
To activate tab completion for the .NET SDK, see Enable tab completion.
Implicit restore
You don't have to run dotnet restore because it's run implicitly by all commands that require a restore to occur, such as dotnet new, dotnet build, dotnet run, dotnet test, dotnet publish, and dotnet pack. To disable implicit restore, use the --no-restore option.
The dotnet restore command is still useful in certain scenarios where explicitly restoring makes sense, such as continuous integration builds in Azure DevOps Services or in build systems that need to explicitly control when the restore occurs.
For information about how to manage NuGet feeds, see the dotnet restore documentation.
Arguments
TEMPLATEThe template to instantiate when the command is invoked. Each template might have specific options you can pass. For more information, see Template options.
You can run
dotnet new listto see a list of all installed templates.The
searchcommand should be used to search for templates in NuGet.org.For a list of templates that ship with the .NET SDK, see Preinstalled templates.
Options
--dry-runDisplays a summary of what would happen if the given command were run if it would result in a template creation.
--forceForces content to be generated even if it would change existing files. This is required when the template chosen would override existing files in the output directory.
-
-?|-h|--helpPrints out a description of how to use the command.
-lang|--language {C#|F#|VB}The language of the template to create. The language accepted varies by the template (see defaults in the arguments section). Not valid for some templates.
Note
Some shells interpret
#as a special character. In those cases, enclose the language parameter value in quotes. For example,dotnet new console -lang "F#".-n|--nameThe name for the created output. If no name is specified, the name of the current directory is used.
-f|--frameworkSpecifies the target framework. It expects a target framework moniker (TFM). Examples: "net6.0", "net7.0-macos". This value will be reflected in the project file.
-no-update-checkDisables checking for template package updates when instantiating a template. Available since .NET SDK 6.0.100. When instantiating the template from a template package that was installed by using
dotnet new --install,dotnet newchecks if there is an update for the template. Starting with .NET 6, no update checks are done for .NET default templates. To update .NET default templates, install the patch version of the .NET SDK.-o|--outputLocation to place the generated output. The default is the current directory.
--projectThe project that the template is added to. This project is used for context evaluation. If not specified, the project in the current or parent directories will be used. Available since .NET SDK 7.0.100.
-d|--diagnosticsEnables diagnostic output. Available since .NET SDK 7.0.100.
-
-v|--verbositySets the verbosity level of the command. Allowed values are
q[uiet],m[inimal],n[ormal],d[etailed], anddiag[nostic]. For more information, see LoggerVerbosity.
Template options
Each template may have additional options defined. For more information, see .NET default templates for dotnet new.
Examples
Create a C# console application project:
dotnet new consoleCreate an F# console application project in the current directory:
dotnet new console --language "F#"Create a .NET Standard 2.0 class library project in the specified directory:
dotnet new classlib --framework "netstandard2.0" -o MyLibraryCreate a new ASP.NET Core C# MVC project in the current directory with no authentication:
dotnet new mvc -au NoneCreate a new xUnit project:
dotnet new xunitCreate a global.json in the current directory setting the SDK version to 8.0.101:
dotnet new globaljson --sdk-version 8.0.101 --roll-forward latestFeatureShow help for the C# console application template:
dotnet new console -hShow help for the F# console application template:
dotnet new console --language "F#" -h
See also
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
