I have the following code in a
In the NuGet package manager, it says that I have Microsoft.NETCore.App version 1.0.5
Now lets say I have the following code in the same
The NuGet package manager will now say that I have Microsoft.NETCore.App version 1.1.4
I'm essentially trying to use the latest framework before .NETCore 2.0 (having some EF issues when I converted) which would be .NETCore 1.1.4 but the multiple Framework attributes in
csproj make me unsure which tag to use. I was unable to find any resources that clearly distinguishes the differences between the two.
TargetFramework is used by NuGet to resolve dependencies and determine the assets to be used for compiling and building the application. (Behind the scenes, a few more properties like
TargetFrameworkVersion come into play but the SDK abstracts it to a simpler
TargetFramework for frameworks it knows about).
RuntimeFrameworkVersion is specific to .NET Core /
netcoreapp. The SDK will inject a dependency on
Microsoft.NETCore.App for the version that
RuntimeFrameworkVersion is set to or use the latest version it knows about for .NET Core < 2.0. The resolved version is then written to the
runtimeconfig.json file for the .NET Core host framework resolver to resolve the version of the shared framework to load (=> .NET Core 1.1.4 runtime for example).
The reason you are able to use
netcoreapp1.0 is because the NuGet package actually contains the necessary assets to build .NET Core 1.0.* applications. However the tooling doesn't know this so you'll get a .NET Core 1.0 app but it will be loaded by the 1.1 framework because that's what ends up in the
The important difference is:
dotnet publish -r win7-x64)
1.0.3but you have the
1.0.5runtime installed, the
1.0.5runtime will be used automatically.
RuntimeFrameworkVersionand a new version of the SDK is released that knows about newer patch versions of .NET Core, it will use the newest version automatically. If you set the version explicitly, you may not be up-to-date without editing the project file.
RuntimeFrameworkVersionis also the minimum runtime that the application will load - if you set it to
1.0.4and try to run on a machine that only has
1.0.3installed, the application will not start unless you edit the
RuntimeFrameworkVersioncan be set to a floating version, which is useful when targeting preview versions or daily builds, e.g.
2.1.0-preview1-*would resolve to the newest
preview1version available on the configured NuGet feeds.
Apart from these, there are only a few reasons to build using a higher version of
Microsoft.NETCore.App, like a build bugfix for the
In .NET Core 2.0, the version of
RuntimeFrameworkVersion will always be
2.0.0 for "portable applications" (non-self contained) because the implementation of the framework is no longer provided by the dependencies of
Microsoft.NETCore.App and this NuGet package is only used to provide reference assemblies for compilation.
From the docs, you should use runtimeframeworkversion only
If you need a specific version of the runtime when targeting .NET Core, you should use the property in your project (for example, 1.0.4) instead of referencing the metapackage.