Skip to content
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

dotnet-scaffold command #4588

Closed
prafullbhosale opened this issue Dec 15, 2015 · 1 comment
Closed

dotnet-scaffold command #4588

prafullbhosale opened this issue Dec 15, 2015 · 1 comment
Milestone

Comments

@prafullbhosale
Copy link

dotnet-scaffold

NAME

dotnet-scaffold -- Code Generation tools for .Net framework

SYNOPSIS

dotnet-scaffold [options] [generator specific options]

DESCRIPTION

The dotnet-scaffold command is used to scaffold code for your application. Scaffolded code is generated by code generators. The code generators are specified as dependencies in the application's project.json. Every code generator is identified by a 'generator-name'. Only one 'generator' can be invoked by a command. (i.e. cannot chain multiple code generators in a single command)
The generator can be installed as a nuget package using the 'dependencies' specified. If the specified dependencies could not be installed, the command will exit with an error.
If no 'generator' is found the command will exit with an error.
If more than one 'generator' is found with the same name, the command will exit with an error.

Options
-p, --project [path] Path to project.json

-r, --relativeOutputPath [path] **
Path relative to the project.json where the scaffolded code should be created

-d, --dependencies [dep1:ver1 dep2:ver2 …]
A delimited list of nuget packages that are needed for the generator.

-n, --name [Name] **
Name of the primary class/ file being generated.

-f, --force **
Flag to indicate whether to overwrite existing files.

[generator specific options] **
Options and flags that can be used by individual generators.

** These options will be passed to the specific generator being invoked and the behavior will be controlled by the specific generator.

EXAMPLES

dotnet scaffold controller --project .\project.json --relativeOutputPath .\Controllers --name EmptyController --noViews

dotnet scaffold view --project .\project.json --relativeOutputPath .\Views --name EmptyView

@blackdwarf blackdwarf self-assigned this Dec 16, 2015
@prafullbhosale
Copy link
Author

Right now we do not want to expose scaffolding via command line. So closing this issue now.

wli3 referenced this issue in wli3/cli Jul 14, 2017
Testplatform release 15.0.0-preview-20161216-01
@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the Backlog milestone Jan 31, 2020
rainersigwald pushed a commit that referenced this issue Jul 20, 2020
…0200526.1 (#4588)

Microsoft.Build.Localization , Microsoft.Build
 From Version 16.7.0-preview-20271-03 -> To Version 16.7.0-preview-20276-01

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants