In late 2016, we started on the journey of improving the docs experience for NuGet with the revamped docs experience. Continuing that journey, today we are announcing the move to docs.microsoft.com/nuget. Given how NuGet has grown to become an integral part of the Visual Studio and .NET ecosystems,
Last month, we launched a preview of the revamped Nuget docs experience. We made a number of improvements:
New quick-starts for creating and consuming packages.
End to end guides for new platforms such as .NET Standard and UWP.
A simpler and more intuitive organization of topics.
Update 9/20 (11:00 A.M PST): The revamped NuGet Docs experience is now live on docs.nuget.org. Read more about it here – New experience for NuGet Documentation
docs.nuget.org is the authoritative guide on everything NuGet. It is used as reference by nearly 180k developers with over 500k page views a month.
A question that comes up from time to time is: how does Visual Studio 2015 add references when using project.json files in conjunction with a csproj without modifying the csproj file? This is a good question and demonstrates some of our strategy to help make NuGet easier to integrate into project systems without having to teach NuGet how to work with every project system.
The NuGet community is awesome; involved and eager to build software to make it easy for use in bigger projects that the components and libraries that they themselves are building. Every now and again, community members can get a little too eager.
In the last few months we have constantly moved the issues and all new code base to GitHub. Today we moved the last bits of code from CodePlex to GitHub. We have stopped monitoring the CodePlex site completely, and will not be taking further looks at reports there or pull requests.
You’ve probably seen the cool announcements from Microsoft about the new Community Edition of Visual Studio and the upcoming Visual Studio 2015 release in the new year. We at the NuGet team have been ramping up our tools to support the new Visual Studio with a better visual experience and a better command-line experience.
Have you ever seen this error before?
Doesn’t it make you want to yell and scream at NuGet, “Why did you just show it to me if I couldn’t install it!?‽”
Yeah, it makes us want to yell and scream too,
Blog Redesign is LIVE!
What better way to announce upcoming website redesigns than by implementing that redesign on our blog? Earlier today, we deployed changes to http://blog.nuget.org that apply a new visual design that we expect to carry over to the docs and gallery sites too.
Over the last couple of years, we’ve had the chance to meet with many individuals who both use and contribute to NuGet. One of the questions that has come up on more than one occasion pertains to how decisions get made for NuGet,