--- title: Speeding up ASP.NET vNext package restore | daily.dev description: When multiple NuGet feeds are configured on a machine, ASP.NET vNext's kpm restore checks every one of them for each dependency in project.json, slowing down... canonical: https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Speeding up ASP.NET vNext package restore | daily.dev og:description: When multiple NuGet feeds are configured on a machine, ASP.NET vNext's kpm restore checks every one of them for each dependency in project.json, slowing down... og:url: https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx og:image: https://api.daily.dev/og/posts/97TTyywsX.png og:image:alt: Speeding up ASP.NET vNext package restore og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Speeding up ASP.NET vNext package restore **[Maarten Balliauw](https://daily.dev/sources/maartenballiauw)** · 3 min read · 0 upvotes · 0 comments ## Summary When multiple NuGet feeds are configured on a machine, ASP.NET vNext's kpm restore checks every one of them for each dependency in project.json, slowing down package restore considerably. Adding a clear element to the project's NuGet.config file removes the inherited machine-level feeds, letting the project explicitly define only the feeds it actually needs, which speeds up restores for everyone working on that codebase. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is kpm restore slow in ASP.NET vNext when I have multiple NuGet feeds configured? ASP.NET vNext's kpm restore checks every NuGet feed configured on the machine for each dependency listed in project.json, because NuGet.config files inherit feed definitions from machine-level configuration. With five feeds configured, for example a personal MyGet feed, a TeamCity feed, a local filesystem feed, the ASP.NET vNext MyGet feed, and NuGet.org, each gets queried repeatedly, slowing the restore. _Developers chasing slow package restores can compare fixes like this one on daily.dev._ ### How do I stop NuGet.config from inheriting machine-level package sources in my project? Add a clear element inside the packageSources section of the project's NuGet.config file. This removes all feeds inherited from machine-level configuration, leaving only the feeds explicitly listed in that file, such as an AspNetVNext MyGet feed and NuGet.org, so restores only check relevant sources. _Anyone tuning NuGet configuration can find practical config tricks like this on daily.dev._ ## Similar posts on daily.dev - [NuGet Package Pruning: Cleaner Dependencies and Actionable Vulnerability Reports](https://daily.dev/posts/nuget-package-pruning-cleaner-dependencies-and-actionable-vulnerability-reports-to2rg1k06) · .NET Blog · 30 upvotes · 0 comments - [Enhanced security in NuGet for .NET 10](https://daily.dev/posts/enhanced-security-in-nuget-for-net-10-az3nuw9gp) · The Art of Simplicity · 8 upvotes · 0 comments - [The Complete Guide to Creating NuGet Packages in .NET](https://daily.dev/posts/the-complete-guide-to-creating-nuget-packages-in-net-4carsceoo) · We Are .NET · 0 upvotes · 0 comments - [Why ASP.NET Core Feels Fast Locally but Slow in Production](https://daily.dev/posts/why-asp-net-core-feels-fast-locally-but-slow-in-production-mtgpu8lqk) · C\# Corner · 42 upvotes · 0 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#nuget](https://daily.dev/tags/nuget) [View this post on daily.dev](https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Speeding up ASP.NET vNext package restore","url":"https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx"},"datePublished":"2026-10-04T13:04:26.636Z","dateModified":"2026-10-04T13:06:29.453Z","description":"When multiple NuGet feeds are configured on a machine, ASP.NET vNext's kpm restore checks every one of them for each dependency in project.json, slowing down...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/841095e1d6652c2f09abf9764348b5bf?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/841095e1d6652c2f09abf9764348b5bf?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Maarten Balliauw","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Maarten Balliauw","logo":"https://media.daily.dev/image/upload/s--rOTg3VYO--/f_auto,q_auto/v1791119043/logos/maartenballiauw?_a=BAMAMicg0","url":"https://daily.dev/sources/maartenballiauw"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,nuget","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Maarten Balliauw","item":"https://daily.dev/sources/maartenballiauw"},{"@type":"ListItem","position":3,"name":"Speeding up ASP.NET vNext package restore"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/speeding-up-asp-net-vnext-package-restore-97ttyywsx#faq","mainEntity":[{"@type":"Question","name":"Why is kpm restore slow in ASP.NET vNext when I have multiple NuGet feeds configured?","acceptedAnswer":{"@type":"Answer","text":"ASP.NET vNext's kpm restore checks every NuGet feed configured on the machine for each dependency listed in project.json, because NuGet.config files inherit feed definitions from machine-level configuration. With five feeds configured, for example a personal MyGet feed, a TeamCity feed, a local filesystem feed, the ASP.NET vNext MyGet feed, and NuGet.org, each gets queried repeatedly, slowing the restore. Developers chasing slow package restores can compare fixes like this one on daily.dev."}},{"@type":"Question","name":"How do I stop NuGet.config from inheriting machine-level package sources in my project?","acceptedAnswer":{"@type":"Answer","text":"Add a clear element inside the packageSources section of the project's NuGet.config file. This removes all feeds inherited from machine-level configuration, leaving only the feeds explicitly listed in that file, such as an AspNetVNext MyGet feed and NuGet.org, so restores only check relevant sources. Anyone tuning NuGet configuration can find practical config tricks like this on daily.dev."}}]} ```