I think we would need it BEFORE the conversion

Sorry, you'd need what before the conversion?

the situation just before you run convert.

can you upload a zip with that?

It is just file > new project. I put it in https://github.com/stimms/PaketReferenceBug/tree/before_conversion

I get a paket.dependencies file with

source C:\Users\Steffen\.dotnet\NuGetFallbackFolder
source https://www.nuget.org/api/v2/

nuget Microsoft.ApplicationInsights.AspNetCore 2.0.0
nuget Microsoft.AspNetCore 1.1.2
nuget Microsoft.AspNetCore.Mvc 1.1.3
nuget Microsoft.AspNetCore.StaticFiles 1.1.2
nuget Microsoft.Extensions.Logging.Debug 1.1.2
nuget Microsoft.VisualStudio.Web.BrowserLink 1.1.2

and paket.references with

Microsoft.ApplicationInsights.AspNetCore
Microsoft.AspNetCore
Microsoft.AspNetCore.Mvc
Microsoft.AspNetCore.StaticFiles
Microsoft.Extensions.Logging.Debug
Microsoft.VisualStudio.Web.BrowserLink

that looks mostly correct.

source C:\Users\Steffen\.dotnet\NuGetFallbackFolder

is probably not something I want to remove and cli tool conversion could be done. But what are you missing?

@stimms I think that is by purpose, because Paket "replaces" PackageReference items in the project with paket.dependencies and paket.references.

I think all you are missing is a simple dotnet restore after Step 3. @forki shouldn't that be working?

@inosik I have currently no idea what the bug is about. But I improved convert to understand cli references as well :P

Closing as fixed