dotnet / dotnet/templating

dotnet new - Option to create solution implicitly when project is created

Open
#3,782 2 comments 0 reactions 0 assignees View on GitHub
area: authoring feature Priority:2 triage:transfer-to-sdk triaged
Dominant language
No language data
Stars
1.7k
Forks
399
Avg merge
3d 5h
Merged PRs (30d)
39

Description

When a new project is created, can we consider an option to create a new solution as well ?

I can think of two workflows for new project creation:

(a) Adding a new project to an existing cohort of projects (which may already contain a solution)
(b) Instantiating a brand new cohort of project(s), which could use a solution file for working with IDE.

I'm interested in improving the experience of the second (b) workflow, which works like this today:

```pwsh
dotnet new $template
dotnet new sln
dotnet sln add $project
// Use sln
```

I'd like to propose a switch addition to `dotnet new ` - `--create-solution | -sln` - which will much like `dotnet new sln`.

The updated `dotnet new` would look like this:

```powershell
dotnet new [--dry-run] [--force] [-lang|--language {"C#"|"F#"|VB}] [-sln|--create-solution]
[-n|--name ] [-o|--output ] [Template options]

dotnet new -h|--help
```

For example, `dotnet new classlib -sln` would generate `classlib.csproj` as well as `classlib.sln`, and `classlib.csproj` to `classllib.sln`.

Similar to `dotnet new sln`, if a solution file already exists in the location, an error would occur.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.