`dotnet completions script pwsh` is very different from https://learn.microsoft.com/en-us/dotnet/core/tools/enable-tab-autocomplete#powershell

[Frulfump]

Describe the bug

Unsure of what the practical differences (perf, usability etc) is and which to prefer (#50065 might currently mean that the linked alternative is preferred (but I guess setting DOTNET_NOLOGO is a workaround for that?))

To Reproduce

➜ dotnet completions script pwsh

Compare with
https://learn.microsoft.com/en-us/dotnet/core/tools/enable-tab-autocomplete#powershell

1387 lines vs 6 lines
The docs page doesn't mention the command, but maybe it should? EDIT2: That's tracked here dotnet/docs#46935
EDIT: Didn't realize this was new in .NET 10, here's some docs for it https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-10/sdk#native-shell-tab-completion-scripts

These scripts improve usability by providing faster and more integrated tab-completion features.

Exceptions (if any)

N/A

Further technical details

details of dotnet --info

.NET SDK: Version: 10.0.100-preview.7.25380.108 Commit: 30000d883e Workload version: 10.0.100-manifests.8bb6be96 MSBuild version: 17.15.0-preview-25380-108+30000d883

Runtime Environment:
OS Name: Windows
OS Version: 10.0.19045
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.100-preview.7.25380.108\

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
Workloads are configured to install and update using workload versions, but none were found. Run "dotnet workload restore" to install a workload version.

Host:
Version: 10.0.0-preview.7.25380.108
Architecture: x64
Commit: 30000d883e

.NET SDKs installed:
8.0.413 [C:\Program Files\dotnet\sdk]
9.0.304 [C:\Program Files\dotnet\sdk]
10.0.100-preview.7.25380.108 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.0-preview.7.25380.108 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.0-preview.7.25380.108 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.0-preview.7.25380.108 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
None

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version

N/A

[baronfel]

@Frulfump I'm going to close this since you found your answer - we just need to doc the new feature. The new static scripts are the recommended way forward for us for a number of reasons

• much faster because they prevent needing to span processes for most common completion tasks
• remain in-sync with the current version of dotnet automatically
• retain the dynamic aspects of completions when necessary
• a sharable foundation for completions for all System.CommandLine-based applications

[Frulfump]

Sounds good! Thanks for the additional details!