Found a workaround, and it explains partly why the local nuget cache isn't working.
If you a local version of all the packages and edit the AuthServer.csproj
<ItemGroup> <PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="1.0.0-rc.*" /> </ItemGroup>
if you change this to
<ItemGroup> <PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="1.0.0" /> </ItemGroup>
this seems to make the nuget version match up locally and you can build
Its unacceptable for our development environment and production deployments to be dependent on such a flimsy service. Its even more unacceptable to have no response on such a critical issue or any escalation procedure.
In our experience we have regular blips in the abp nuget feed, we are going to have to look at alternatives for our development and deployment environment I think.
In ABP IO the uptime of the nuget server is critical. We regularly seem to have issues with downtime or blips with certain packages, this is a larger discussion that needs to be had. In the short term, it would be very useful to have a is it up page, with a history of down times, scheduled maintenance etc.
Similar to https://status.slack.com/ or many others