NET Standard 2.0, it means that the package is built and designed to work with any runtime that supports the. NET 4.7, they may need to update the NuGet packages they use to maintain compatibility and ensure their application continues to work as expected. If a developer upgrades their project’s target framework to. NET Framework 4.6 ( net46 for short), that means the package is built and designed to work with applications that are built using the. NET Standard version.įor example, if a package specifies that it targets the. The target framework is typically specified using a specific. When a package is created, the developer specifies which target framework(s) the package supports. NET framework that a NuGet package is built and designed to work with. We wanted to take this opportunity to put filters in a logical place where they’re always available and we moved the sort options to a more accessible location. NET framework or packages still targeting the framework you are, this feature is here to help.įinally, you may have noticed some elements were moved on the search page. Whether you are looking for compatible packages on the latest. NET framework is backwards compatibility, which enables developers to upgrade their applications and packages to newer versions of the framework without having to completely rewrite their code. If you’d like to get more specific about the version, you can expand the parent element and then select a combination of known target frameworks. NET including net5.0 through net7.0 and provides at least one of these versions with a framework asset respectfully. NET in this example will match packages that are built for modern. NET frameworks you’re interested in a package providing assets for. The first thing you might notice is that there is a new “Frameworks” filter on the left where you can select from a collection of. Today, we are announcing a new feature that will allow you to search by a target framework on. Last year, we brought a new feature to improve the way you assess target framework compatibility of a NuGet package through a new “Frameworks” tab.
0 kommentar(er)
