sln add globbing patterns fail

This pertains to dotnet/docs dotnet/sdk#5373

Per the documentation this should work.

It is not clear if this is a bug or a documentation problem.

Steps to reproduce

Given the following file structure:

. ├── Api │   ├── Api.csproj │   ├── Controllers │   └── wwwroot ├── complex-solution.sln ├── Data │   └── Data.csproj ├── Domain │   └── Domain.csproj └── Logging └── Logging.fsproj

Add projects to my solution using blobs: dotnet sln complex-solution.sln add **/*

Expected behavior

The output for the first task should look something like:

Project `Api/Api.csproj` added to the solution.
Project `Data/Data.csproj` added to the solution.
Project `Domain/Domain.csproj` added to the solution.
Project `Logging/Logging.fsproj` added to the solution.

Actual behavior

Output from first task:

Project `Api/Controllers` does not exist.
Project `Api/obj` does not exist.
Project `Api/wwwroot` does not exist.
Project `Data/obj` does not exist.
Project `Domain/obj` does not exist.
Project `Logging/obj` does not exist.
.NET Add project(s) to a solution file Command

Usage: dotnet sln <SLN_FILE> add [options] [args]

Arguments:
  <SLN_FILE>  Solution file to operate on. If not specified, the command will search the current directory for one.

Options:
  -h|--help  Show help information

Additional Arguments:
 Add a specified project(s) to the solution.

The end result is that nothing is adde to the solution:

dotnet sln complex-solution.sln list

No projects found in the solution.

Side note

The commands work fine when I substitute **/* with **/*.{csproj,fsproj}

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     fedora
 OS Version:  24
 OS Platform: Linux
 RID:         fedora.24-x64
 Base Path:   /opt/dotnet/sdk/1.0.1

[livarcocc]

Globbing is actually a feature of the shell and not of the CLI. For instance, you get globbing at bash, because bash implements it, we have no intention of adding our own globbing at the CLI.

[Rudithus]

Yes I’ve just tried it on bash and globbing is working as expected. It’s weird because ls **/*.csproj command is working fine on powershell. I would have thought this meant it would work for dotnet cli aswel.