The ID prefix of this package has been reserved for one of the owners of this package by Prefix Reserved
This is a prerelease version of Prism.Forms.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Prism.Forms --version
NuGet\Install-Package Prism.Forms -Version
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Prism.Forms" Version="" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Prism.Forms --version
#r "nuget: Prism.Forms,"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Prism.Forms as a Cake Addin
#addin nuget:?package=Prism.Forms&version=

// Install Prism.Forms as a Cake Tool
#tool nuget:?package=Prism.Forms&version=

Prism provides an implementation of a collection of design patterns that are helpful in writing well structured and maintainable XAML applications, including MVVM, dependency injection, commanding, event aggregation, and more. Prism's core functionality is a shared code base in a Portable Class Library targeting these platforms; WPF, Windows 10 UWP, and Xamarin Forms. Features that need to be platform specific are implemented in the respective libraries for the target platform. Prism for Xamarin.Forms helps you more easily design and build rich, flexible, and easy to maintain Xamarin.Forms applications.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp1.0 was computed.  netcoreapp1.1 was computed.  netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard1.0 is compatible.  netstandard1.1 was computed.  netstandard1.2 was computed.  netstandard1.3 was computed.  netstandard1.4 was computed.  netstandard1.5 was computed.  netstandard1.6 was computed.  netstandard2.0 was computed.  netstandard2.1 was computed. 
.NET Framework net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen30 was computed.  tizen40 was computed.  tizen60 was computed. 
Universal Windows Platform uap was computed.  uap10.0 was computed. 
Windows Phone wp8 was computed.  wp81 was computed.  wpa81 was computed. 
Windows Store netcore was computed.  netcore45 was computed.  netcore451 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (44)

Showing the top 5 NuGet packages that depend on Prism.Forms:

Package Downloads

Prism Forms Plugin to provide Popup Navigation working with the Rg.Plugins.Popup library

Prism.Unity.Forms The ID prefix of this package has been reserved for one of the owners of this package by

Use these extensions to build Xamarin.Forms applications with Prism and Unity.

Prism.DryIoc.Forms The ID prefix of this package has been reserved for one of the owners of this package by

Use these extensions to build Xamarin.Forms applications with Prism and DryIoc.


The home module contains common functionality and essetntials required to build an app home page


The events module contains common functionality and essetntials required to build apps that have event specific functionality

GitHub repositories (10)

Showing the top 5 popular GitHub repositories that depend on Prism.Forms:

Repository Stars
Makes things cross-platform
Samples that demonstrate how to use various Prism features with Xamarin.Forms
SettingsView for Xamarin.Forms
Xamarin.Forms goodlooking UI sample
Version Downloads Last updated
9.0.401-pre 1,495 2/14/2024
9.0.271-pre 3,289 10/8/2023
9.0.264-pre 2,807 10/7/2023
8.1.97 914,892 5/24/2021 710,205 10/21/2020 7,131 8/25/2020 7,058 5/5/2020 4,849,731 11/21/2019 211,288 7/24/2019 11,228 6/11/2019 6,721 5/6/2019 9,277 2/20/2019 5,395 12/4/2018 10,134,910 10/15/2018 6,662 9/20/2018 39,027 6/15/2018 5,464 5/9/2018 21,242 4/2/2018 269,672 1/22/2018 25,987 1/12/2018 15,652 12/7/2017 10,570 11/16/2017 23,293 10/13/2017 8,938 10/6/2017
7.0.0-pre1 5,848 9/22/2017
6.3.0 196,136 3/25/2017
6.3.0-pre2 6,406 2/26/2017
6.3.0-pre1 16,035 11/2/2016
6.2.0 45,616 8/9/2016
6.1.0-pre7 4,344 7/15/2016
6.1.0-pre6 4,244 6/21/2016
6.1.0-pre5 6,136 5/5/2016
6.1.0-pre4 5,687 4/5/2016
6.1.0-pre3 8,436 1/20/2016
6.1.0-pre2 3,962 12/10/2015
6.1.0-pre1 3,906 12/3/2015
6.0.1 10,558 10/26/2015
6.0.0 5,500 10/14/2015
5.9.0-pre2 3,582 10/12/2015
5.8.0-pre1 3,851 10/8/2015
5.7.0-pre3 4,198 6/10/2015
5.7.0-pre2 3,370 6/10/2015
5.7.0-pre1 3,942 6/8/2015
5.6.1-pre1 3,834 3/24/2015

## Prism.Core
* .NET Standard Support
* Added method to clear all errors on ErrorsContainer
* Add capability to DelegateCommand's ObservesProperty to observe properties of complex types
`ObservesProperty(() => Property.NestedProperty.NestedPoperty)`

## Prism.Forms
* Fixed #683: .NET Standard support
* Fixed #765: Deep linking within a NavigationPage results in an incorrect ContentPage Title on Android
* Fixed #1008: NavigationParameters: Not possible to specify parent type as generic parameter T
* Fixed #1024: XF: NavigationService swallowing Exceptions
* Fixed #1025: Xamarin.Forms deprecated the Device.OS property in favor of the RuntimePlatform property.
* Fixed #1027: Support macOS
* Fixed #1044: When Detail of MasterDetailPage is null, Modal Navigation is possible
* Fixed #1045: When calling NavigateAsync with NavigationPage, old page's Destroy on the stack is not called
* Fixed #1046: When calling DeepLink from Navigation Stack, the second page becomes Modal navigation
* Fixed #1054: When deep linking within NavigationPage, page order is reversed
* Fixed #1063: Master of MasterDetailPage will not be destroyed
* Fixed #1085: Error occurs if null path is specified in EventToCommandBehavior
* Fixed #1089: DebugLogger does not work in nuget-package
* Fixed #1132: Prism Forms Modularity extension methods
* Fixed #1133: IModuleCatalog AddModule returns wrong type
* Fixed #1139: Modularity Enhancements
* Fixed #1076: IActiveAware not working when ContentPage (as child of a TabbedPage) is wrapped into a NavigationPage

* deprecated OnPlatform methods
* added DeviceRuntimePlatform property - this mimics the XF API and returns a string
* added RuntimePlatform property which returns an Enum of type RuntimePlatform and wraps the XF string-based values

**Container Extensions**
* deprecated the RegisterTypeForNavigationOnPlatform signature that requires explicit platform parameters
* added new signature that accepts new IPlatform objects
Container.RegisterTypeForNavigationOnPlatform<MainPage, MainPageViewModel>("Main",
new Platform<MainPage_Android>(RuntimePlatform.Android),
new Platform<MainPage_iOS>(RuntimePlatform.iOS));

# TabbedPage Navigation Behavior Change - BREAKING
## Current Behavior (v6.3.0)
`NavigateAsync("TabbedPage/ViewA/ViewB")` will select the tab ViewA in the TabbedPage if it exists, then continue navigating.  If ViewA does not exist as a tab, then you will continue to navigate as expected.

`NavigateAsync("TabbedPage/NavigationPage/ViewA/ViewB")` would search the TabbedPage for the first instance of a tab that was a NavigationPage, then navigate within the Navigation page the remaining ViewA and ViewB pages.  This provided the ability to deep link into a tab's nested navigation page, but there was no way to opt-out of this behavior.

Also, the INavigationAware methods did not get called to all tabs meaning that you would be responsible for forwarding any parameters to all your tabs.

## New Behavior
`NavigateAsync("TabbedPage/ViewA/ViewB")` will **no longer** select any tabs, but rather continue processing the navigation as separate pages on the navigation stack.

If you wish to select a tab, you will now use a parameter called "selectedTab" to indicate which tab you would like to select.


This will navigate to the TabbedPage, selected the "MiddleTab" and continue navigating ViewA and ViewB onto the navigation stack.

For tabs that are wrapped inside a NavigationPage, you can use the "|" symbol to indicate the hierarchy.


There is a constant in the `KnownNavigationParameters` called `SelectedTab` that you can use instead of a string.


This will search each tab to see if it is a navigation page and if the first page on the stack matches "MiddleTab".  This is much more flexible than the existing behavior as before it would take the first instance of the NavigationPage found.  Now you can choose which tab exactly.

Some INavigationAware methods are now fired on all Tabs:
- OnNavigatingTo will be invoked on the TabbedPage and ALL TABS.
- OnNavigatedTo will be invoked on the TabbedPage and only the SELECTED TAB.
- OnNavigatedFrom will be invoked on the TabbedPage and only the SELECTED TAB.

**Note**: the parameter key `selectedTab` is now a reserved parameter name.  Similar to a reserved keyword in C#.  If you use this in your app as a key, you may experience undesired behavior.

**Note**: At this time there is no native support for deep linking into a Tab that is a navigation page.  Please let me know if you need this functionality.