Alias .NET Restore... commands to dotnet restore...

[spboyer]

Currently .NET commands are only surfaced in the command pallete when .NET is typed. Typing dotnet should also surface the core commands for .NET Core.

cc:/ @timheuer

[rchande]

@spboyer It's not the intention of the C# extension to expose dotnet.exe through the command palette.

We offer commands for performing restore on a specific project, or on all projects we can see. We could potentially alias them with a version that starts with "dotnet".

We offer a separate command to generate VS Code tasks/launch assets, but that doesn't really relate to any feature of dotnet.exe.

[spboyer]

Offering only restore appears incomplete knowing there are other operations we would inherently perform on .NET projects we could see.

Not looking to expose all functionality of the dotnet.exe however perhaps this extension should instead of a one off wrapping the exe itself and duplicating some of the operations here?

The intent of the issue was to alias “dotnet” when typed to surface the existing options prefaced with or containing “.NET”

[rchande]

@spboyer

The intent of the issue was to alias “dotnet” when typed to surface the existing options prefaced with or containing “.NET”

Great! We're on the same page here. Let's use this issue to track that.

Offering only restore appears incomplete

We've exposed a bunch of functionality in a way that's more idiomatic to VS Code. For example, if you use the command .NET: Generate Assets for Build and Debug, we generate the appropriate VS Code configuration to wire up the VS Code Build and Run commands, which may shell out to dotnet.exe. This obviously gives you the equivalent to dotnet build and dotnet run. We offer restore as a named command because it doesn't map onto a VS Code concept by itself, and you might want to restore without building (if you changed a project file).

@timheuer actually recently updated our tasks generation to add publish and I think that's probably a better way to go than adding individual aliased commands (#2903). What do you think?

[spboyer]

Agreed on all points here.

[JoeRobich]

Closing due to lack of activity.