Migrating a pure dotnet-core project does not create a solution

Steps to reproduce

dotnet migrate on a project that only contains project.json projects (example)

Expected behavior

The projects are migrated to csproj and a solution is created OR the tool chain allows multiple projects to be specified as before.

Actual behavior

The projects are migrated, but a solution is not created. This means there is no easy way to restore and build, since dotnet restore only allows you to specify one project at a time and dotnet build seems to want a solution now instead of searching for projects. Perhaps I missed a communication?

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-rc4-004771)

Product Information:
 Version:            1.0.0-rc4-004771
 Commit SHA-1 hash:  4228198f0e

Runtime Environment:
 OS Name:     arch
 OS Version:  
 OS Platform: Linux
 RID:         ubuntu.14.04-x64
 Base Path:   /opt/dotnet/sdk/1.0.0-rc4-004771

[dasMulli]

Luckily, you no longer need to hack one together manually 😄 🎉

MacBook-Pro:foobar martin$ dotnet new solution
Content generation time: 20.3027 ms
The template "Solution File" created successfully.
MacBook-Pro:foobar martin$ dotnet sln add **/*.csproj
Project `app1/app1.csproj` added to the solution.
Project `app2/app2.csproj` added to the solution.

[dasMulli]

The executable thing is a standing issue with .net… there are issues both on the cli and corefx for it.

Globbing should be done by the shell here so it probably depends on the shell version and settings (bash 3.2.57(1) on Mac OS in my case). So you could also do it via find . -type f -name '*.csproj' -exec dotnet sln add {} \;