Although PCLs are supported, package authors should support netstandard instead. The dotnet series of monikers should be used in NuGet 3.3 and earlier the netstandard moniker syntax should be used in v3.4 and later. The NuGet Get Nearest Framework Tool simulates what NuGet uses to select one framework from many available framework assets in a package based on the project's framework. NET Standard simplifies references between binary-compatible frameworks, allowing a single target framework to reference a combination of others. Deprecated frameworkĪ number of frameworks are related to and compatible with one another, but not necessarily equivalent: Framework Packages targeting these frameworks should migrate to the indicated replacements. Uap10.0.xxxxx (where 10.0.xxxxx is the target platform min version of the consuming app)
#MONO FRAMEWORK VERSION SUPPORTED WINDOWS 10#
Win10 (not supported by Windows 10 Platform) The various NuGet client tools handle these variations properly, but you should always use canonical TFMs when editing files directly.
Note that some tools, such as dotnet, might use variations of canonical TFMs in some files. The NuGet clients support the frameworks in the table below.
#MONO FRAMEWORK VERSION SUPPORTED CODE#
The NuGet client source code that calculates the tables below is found in the following locations:
0 kommentar(er)
