Here we are again with a new episode of MyGet's NuGet and NPM news from the community! We will look at some interesting blog posts and articles found on the Internet, curated by our MyGet founders Xavier and Maarten. Follow @MyGetTeam on Twitter for more!
The .NET team announced .NET Core, .NET Native and NuGet Updates in VS 2017 RC. Quite a few changes, most notably the improvements in NuGet to use the new
.csproj format and package references therein. And early in February, NuGet 4.0 RC was released as well.
More news from Redmond: NuGet.org now also supports scoped API keys, just like we do. Where on MyGet scope is per feed, NuGet came up with a per-package model. Do check it out!
Will this be the new way of distributing project templates? As NuGet packages? Muhammad Rehan Saeed found a new element that can be used in a
.nuspec and demonstrates Custom Project Templates Using dotnet new.
Puneet Ghanshani describes a way of creating an inventory of packages a solution uses by working with the
NuGet.Core package. Would be great to see something like this as a Visual Studio extension!
Scott Addie wrote a great article, Migration to ASP.NET Core, where he walks through the various considerations and strategies of migrating a .NET codebase to .NET Core. The article covers the various frameworks, targets, the portability analyzer, and more!
Just started looking at the
dotnet command line tool? Steve Smith explains how to add a Nuget Package Using dotnet add.
Managing the life cycle of PowerShell module assets in your Azure Automation accounts can be challenging. Not anymore! Tao Yang explains how you can leverage MyGet to its full extent to make this tedious task a breeze and take full control of your very own PowerShell Gallery, on MyGet.
A fresh firstname.lastname@example.org landed, featuring improved search - faster and more relevant. Debug logs are now saved in the
_cache folder, making it easier to clean them up.
NPM Vet is a new tool that allows us to to quickly visualise the difference between versions defined in our
package.json and versions installed in the
node_modules folder. In other words: it helps us check for dependency mismatches.