Think of this version as the "platform version" or "OS API version" to disambiguate it from the run-time OS version.
It's used to select the reference assemblies that your project compiles against, and to select assets from NuGet packages. It does not control the OS version that your app or library supports at run time. The version indicates which APIs are available to your app or library. You can also specify an optional OS version at the end of an OS-specific TFM, for example, net6.0-ios15.0. For example, WinForms and WPF projects should target net6.0-windows.Ĭross-platform application models (Xamarin Forms, ASP.NET Core) and bridge packs (Xamarin Essentials) should at least target the base TFM, for example, net6.0, but might also target additional platform-specific flavors to light-up more APIs or features. Platform-specific libraries should target platform-specific flavors. This includes most libraries but also ASP.NET Core and Entity Framework.
#Visual studio net6 portable
Use these guidelines to determine which TFM to use in your app:Īpps that are portable to multiple platforms should target a base TFM, for example, net6.0. For a list of the available symbols, see Preprocessor symbols. To make your app portable across different platforms but still have access to OS-specific APIs, you can target multiple OS-specific TFMs and add platform guards around OS-specific API calls using #if preprocessor directives. (subsequent version of net6.0-maccatalyst) os (+everything else inherited from net6.0) Xamarin.mac (+everything else inherited from net6.0) Xamarin.ios (+everything else inherited from net6.0) Xamarin.android (+everything else inherited from net6.0) Netcoreapp1.3.1 (plus everything else inherited from net5.0) Net1.4 (with NU1701 warning) netcoreapp1.3.1 (warning when WinForms or WPF is referenced) netstandard1.2.1 The following table shows the compatibility of the. NET 5 introduced the net5.0-windows OS-specific TFM, which includes Windows-specific bindings for WinForms, WPF, and UWP APIs.NET 6 and later versions have additional OS-specific TFMs, for example, net6.0-ios. OS-specific TFMs also inherit every API available to their base TFM, for example, the net6.0 TFM.
#Visual studio net6 windows
Specifying an OS-specific TFM makes APIs that are specific to an operating system available to your app, for example, Windows Forms or iOS bindings. The net5.0, net6.0, and net7.0 TFMs include technologies that work across different platforms. NET 5+ OS-specific TFMs.NET 5+ OS-specific TFMs For more information, see the following section. NET 5 and later TFMs include some operating system-specific variations. For example, win81 is an equivalent TFM to netcore451.
The following table shows the target frameworks supported by the. Target frameworkĪ target framework is typically referenced by a TFM. A target framework moniker (TFM) is a standardized token format for specifying the target framework of a. These target framework versions are the latest stable versions. The following table defines the most common target frameworks, how they're referenced, and which version of. NET Standard), the APIs are defined by the NuGet packages included in the app or library. NET Framework, the APIs are defined by the assemblies that the framework installs on a system and may include application framework APIs (for example, ASP.NET).įor package-based target frameworks (for example. For example, an app that targets Xamarin.iOS (for example, Xamarin.iOS10) has access to Xamarin-provided iOS API wrappers for iOS 10, or an app that targets Universal Windows Platform (UWP, uap10.0) has access to APIs that compile for devices that run Windows 10.įor some target frameworks, such as. NET implementation to gain access to implementation-specific APIs. NET Framework using the same codebase.Īn app or library can also target a specific. NET Standard 1.6 and gain access to APIs that function across. NET Standard.NET Standard versions represent standardized sets of APIs across all. You specify the target framework in your project file using a target framework moniker (TFM).Īn app or library can target a version of.
When you target a framework in an app or library, you're specifying the set of APIs that you'd like to make available to the app or library.
0 kommentar(er)
