NuGet PackageReference supported by EPiServer CMS/Commerce?

Vote:
 

Related information https://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html

What worries me is this:

Will existing NuGet packages work if I am using PackageReference for WPF, Windows Forms or ASP.NET projects?

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.

#181832
Aug 31, 2017 11:44
Vote:
 

don't think so. just look into package content :) there is almost everything that is mentioned as not supported

#181976
Sep 06, 2017 15:52
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.