You can see the Target Framework Monikers (TFMs) that each package supports on under the Dependencies section of the package page.Īlthough using the site is an easier method to verify the compatibility, Dependencies information isn't available on the site for all packages.
NET Core, there are a few ways that you can achieve that: Analyze NuGet packages using If you haven't already verified that your converted and upgraded package dependencies work on. It's likely that newer versions of your package dependencies are already compatible with. This can be done with the NuGet Package Manager UI in Visual Studio.
NET.įirst, upgrade your packages to the latest version that you can. Upgrade your NuGet packagesĪfter you migrate your project to the PackageReference format, verify if your packages are compatible with.
To learn how to migrate, see the Migrate from nfig to PackageReference article. If you're using nfig to specify your packages in your project, convert it to the PackageReference format. NET Framework can use PackageReference to specify package dependencies. NET can't use the nfig file for NuGet references. Migrate your NuGet packages to PackageReference NET Framework, consider targeting the latest version of. However, if you don't need to use the library with. NET Standard 2.0 or below ensures that it can be used with both. dll files you reference in your project, but that you don't build yourself. External dependencies are the NuGet packages or.
To identify the unsupported third-party dependencies in your project, you must first understand your dependencies.