NuGet Restore Manager

NuGet Restore Manager

Problem

In VS2015 NuGet employs different mechanisms to initiate restore operation. Support .NET Core and UWP projects. Replace WebTools restore. Enable intellisense early as restore happens. Restore on build, avoid modal restore popup. Support VS "15" project update scenario No-op optimization. project.json changes. Have unified architecture to support all VS project models

Who is the customer?

Software developers using Visual Studio "15" to build .NET Core and UWP applications and libraries.

Evidence

What is the evidence that behaves us to act? Evidence can be impassioned tweets or mails, mile long conversations in issues, rants on blogs, sweet sweet data from telemetry!!! If you can show pain, you can rally the troops.

Solution

Design meeting notes

• How to bootstrap N.R.M. on project open or new?
  • Mef component
  • Second packagedef in vsix
• How to get info from VS at bootstrap time?
  • Packages.config - project directories, packages directory
    • NuGet.Config discovery is expensive
  • UWP Project.json - dg info (needs to keep updated)
• any changes watcher
  • Project.json
  • Settings changes
  • Dependency changes / dg info for uwp (check if we need this as separate update)
  • Lock file presence
• CPS "Restore Nominator" Capability - csproj integration, capabilities?
  • When nominating CPS supplies project dir, intermediate dir, restore output type (uap, netcore), dg graph
• How to block the build until we have full info from VS?
  • Virtual Project?