To work around this, I am creating a new nfig file and populating it with the basic content it needs for my project to work. However, the package restore process decides it needs to check the access to the private/protected repository regardless. I don't want to pull anything from a private repo for my new console app. Notice how we receive an Unauthorized 401 error on the redacted_org url, which is a private repository that I have access to. Įrror: Response status code does not indicate success: 401 (Unauthorized). Info : Restoring packages for C:\code\zimmergren.cli\.Įrror: Unable to load the service index for source. Writing C:\Users\tobia\AppData\Local\Temp\tmpE602.tmpinfo : Adding PackageReference for package '' into project 'C:\code\zimmergren.cli\'. Something I've ran into several times is when running dotnet restore or dotnet add package, the tool throws and error with Unauthorized. However, not its not uncommon to stumble into various issues with NuGet, if you're a dotnet dev. Setting up an entirely new project and getting things off the ground is usually the quickest part of our development process for a project. 💡 TIP: Check out the guidance for building sustainable Azure workloads! 🌿
0 kommentar(er)
