At the moment I\'m porting an asp web api to .Net Core.
The api uses a Class library which provides some implementations of the ActionFilterAttribute class.
You can't (well technically you could via NuGet Fallback, but you shouldn't as it may affect your portability) and you shouldn't.
The .All
package is a convenience meta-package, so you don't need to reference a dozen or other assemblies for even the simplest ASP.NET Core Project.
It's targeting .NET Core for a reason, so you can't use it in .NET Standard.
When you publish your application, the unused packages will be stripped off. When doing a class library you don't want dependency on everything but only the packages which are required by your project.