Matthieu Penant

Same error with PagedList 1.17

Consider [Squirrel](https://github.com/Squirrel/Squirrel.Windows) for auto-updates instead of ClickOnce, and [Chocolatey](https://chocolatey.org/) for first-time install.

@drewnoakes ClickOnce is embed in the build process, which means a specific full build to create the clickonce setup, instead of just taking the output of the build and packaging...

The same error appears with 2.5.48, so something changed in Visual Studio. Error appears after cleaning the package cache.

C++ project (and C++/CLI too) can consume nuget packages in the packages.config way - see native packages: https://docs.microsoft.com/en-us/nuget/guides/native-packages The creation process is kind of painful to do manually - there...

@drewnoakes @somdoron Named Pipes were not considered based on mono incompatibility, but is it still an issue with everything that happened with .net standard since then? System.IO.Pipes is .net standard...

I might need it for some of my projects at some point. If it happens, I would try to implement it with Named Pipes from .Net Standard 2.0.

Same goes for RECS0004, considering the following code: ``` public class AmountTypeEntity : Entity { public AmountTypeEntity() => Initialize("Test"); } ```

Same goes for Task.Run: `Task.Run(() =>_gadgetModules.SendResetSignal())` gives `Task.Run(_gadgetModules.SendResetSignal)` which results in _The call is ambiguous between the following methods or properties: 'Task.Run(Action)' and 'Task.Run(Func)'_

Reference: https://msdn.microsoft.com/en-us/magazine/jj991977.aspx