CODEWITHSUNDEEP
c#nugetasp.net-corepackageasp.net-core-mvc
Ивайло Кенов
Ивайло Кенов

Reputation: 885

Best way to upload multiple .NET Core packages with dependencies to each other to NuGet?

I have .NET Core C# class library projects that I want to upload to NuGet available here.

Some of these packages depend on others from the solution. For example MyTested.AspNetCore.Mvc depends on MyTested.AspNetCore.Mvc.Core.

Since there is slight delay of indexing when uploading a package to NuGet how can I overcome the following problem:

  1. I start uploading packages (CI or manual)
  2. 3 of 9 (or more) packages are already uploaded but the rest are still missing
  3. While I upload them, someone tries to download a package but its dependencies are not indexed yet
  4. He receives an error that a package is missing

What are my best options here?

Should I upload the packages starting from the lowest dependent package and finishing with the most dependent one? Since the number of packages may increase in the future, this may become quite tedious work to manage.

Should I unlist all packages untill they are all uploaded and then list them at once?

Anything else as solution? I wonder how Microsoft is doing with .NET Core and ASP.NET Core where they have hundreds of packages depending on each other.

Upvotes: 0

Views: 139

Answers (1)

Sock
Sock

Reputation: 5413

I believe (remembering from a community standup), that the team uploads all the packages in an un-listed state, then flicks the switch to have them listed/indexed.

Upvotes: 2

Related Questions