Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Paket is very slow with ASP.NET Core 2
See original GitHub issueDescription
Performance is suboptimal when paket is used with ASP.NET Core 2. Just wondering if that is because of microsoft.aspnetcore.all metapackage or issue is the same as in #2827?
Repro steps
-
dotnet new webapi -
download paket.exe (ver 5.153.0), save it to
./paketdirectory -
.\.paket\paket.exe convert-from-nugettakes ~ 5 minutes -
.\.paket\paket.exe updatetakes minutes -
.\.paket\paket.exe add xunittakes minutes
Repro is available here
Expected behavior
It is expected to be much faster.
Actual behavior
Steps 3…5 should not take minutes, but rather seconds. Console output can be observed in my twitter.
Known workarounds
No any.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
or you go to deps file. add it and run install
I think I now understand your issue. You are not complaining about the resolution time, but you want to add couple of packages and resolve only once. is that correct?