Hi Team,
I've checked through and it doesn't seem like anyone has reported this yet. My Nuget feed is only returning the first entry on the list, giving me no options to continue developing, or restore any project.
Any idea if it's something I need to update my side, or if it's not when it will be avaliable again?
6 Answer(s)
-
0
Can you share the logs when you try to build the solution?
Also could you try to restore using the dotnet cli with the following command?
dotnet restore --no-cache --configfile .\NuGet.Config
If there are errors too, please share them with us. -
0
Okay, so I've got an update.
I've ran the restore that you askedm and got a lot of "info : NotFound" appearing. I accidently closed the window trying to grab a screenshit, so I ran it again and now I've got "Restored:" across the board.
I cannot however add a new module. List is still appearing empty, and only Admin.Application appears in the package manager.
Actually, as I've been typing this, I've noticed this occuring.
It's like it can get to the feed, and if I ask for a package explicitly, it lets me get it, but I can't search through packages, only list the top 1.
-
0
Hello,
I have a similar issue... Restore of package is working... In facts, it's the "Commercial Nuget Source" feed that is "kind of broken".
I don't know if it's intended or not, but with the Nuget Package Manager inside visual studio, we cannot browse packages.
My nuget source is set to https://nuget.abp.io/[our own GUID]/v3/index.json as expected...
It's like if your nuget API endpoints are not "fully working" as expected ?!?!?
-
0
-
0
After internal discussion with the core team, I found out that the nuget feeds for commercial are based on a custom nuget server implementation and there wont be any changes made to support the explorer list feature for the commercial nuggets. So there wont be the functionality to search for commercial nuget packages.
If you want to add a module to your solution please use the abp suie or cli to do so.
I refunded the question for you.
-
0
Thank you for the update and clarification. It's strange that it's not a feature you plan to support, but it's nice to know that it's been acknowledged and that it is working as intended.