Our monthly Virtual Happy Hour is happening this week, Fri Feb 23!
Related information https://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
What worries me is this:
While we have done a lot of work to ensure that existing packages on NuGet.org just work with the PackageReference format, there are a few scenarios that will not be supported in the PackageReference world and might impact your ability to migrate away from packages.config. Some examples of scenarios that will not be supported include content folders (we have introduced ContentFiles), XDT transforms, PowerShell scripts i.e. install.ps1 and uninstall.ps1 (only init.ps1 is supported) . If you come across a package you consume in your WPF or Windows Forms app that worked previously but does not work on migrating your project to PackageReference, we would love to hear from you, so that we can investigate what the incompatibilities might be.
don't think so. just look into package content :) there is almost everything that is mentioned as not supported