Prism Framework

Prism is a framework designed for building loosely coupled, maintainable, and testable XAML applications. It supports multiple platforms including WPF, Avalonia, MAUI, Uno Platform, and WinUI.

Prism implements several key design patterns to help structure XAML applications:

• MVVM (Model-View-ViewModel)
• Dependency Injection
• Commands
• EventAggregator

Core functionality is shared via a codebase supporting .NET Standard 2.0, .NET Framework 4.6 / 4.7, and .NET 6.0/.NET 8.0, while platform-specific implementations are provided in dedicated libraries.

Prism 9.0 uses a Dual License model:

• Community License: Free for the vast majority of the community.
• Commercial License: Required for larger organizations to support Prism development.
• Commercial Plus License: Provides access to additional support libraries and a private Discord channel for interacting with the Prism Team.

The HelloWorld.slnx solution file includes Prism library projects.

Important: Do not pass a single -f (target framework) flag to the entire solution. Doing so forces every project in the solution, including Prism.Core, onto a single TFM. Instead, build the HelloWorld.csproj project individually for each TFM as described in the CLI build guides.

Uno prevents using dotnet build for WinUI class libraries that contain XAML (error UNOB0008). To build the Windows TFM, you must use Visual Studio or msbuild.

Use the following command to build with the specific Windows target framework:

msbuild .\e2e\Uno\HelloWorld\HelloWorld.csproj -restore -p:TargetFramework=net10.0-windows10.0.26100

If you encounter a bug, follow these requirements to ensure your report is not closed:

1. Search first: Check existing open and closed issues to see if the bug has already been reported or fixed.
2. Provide a reproduction sample: You MUST create a new, minimal project that focuses ONLY on the necessary steps to reproduce the issue. Issues without a sample app reproducing the issue will be closed.
3. Avoid 'Archaeology': Do not comment on old Pull Requests, commits, or issues. If you find a legitimate issue related to old work, open a new issue and reference the relevant old items.

Prism is distributed under the MIT License "AS IS", without warranty.

• Enterprise Support: For code-level support, architectural guidance, or custom builds, contact the Prism team via https://github.com/PrismLibrary/Prism to inquire about Enterprise support options.
• Community Support: For general questions, use GitHub Discussions on the main Prism repository. Avoid using GitHub Issues for questions; Issues are reserved for feature requests and bug reports.
• Stack Overflow: You may ask questions on Stack Overflow, but note that the Prism team does not monitor that platform.

If you need assistance with Prism, use the following channels:

• Documentation: The official documentation is hosted at docs.prismlibrary.com.
• General Questions: Post in GitHub Discussions.
• Bugs and Feature Requests: Open an issue in the GitHub Issues tracker.
• Enterprise Support: Contact the team via email at support@prismlibrary.com.

Note: The Prism Team does not support or engage with questions on StackOverflow.

Prism is available under two licensing models: the Prism Community License (free) and the Prism Commercial License (paid). You must possess one of these licenses and agree to Prism's terms and conditions to use the software.

Prism Community License Criteria

You qualify for the free Community License only if you meet all of the following requirements:

• Annual gross revenue is less than one million U.S. dollars ($1,000,000.00 USD).
• You have fewer than five (5) total developers.
• You have never received more than $3 million USD in capital from outside sources (e.g., private equity or venture capital).

Prism Commercial License

If you do not meet all the criteria for the Community License, you must purchase a Commercial License. Visit the Prism Library website to explore options.

To use image assets in a shared project, follow these steps:

1. Add the image file to the Assets directory of your shared project.
2. Set the file's Build Action to Content.
3. For optimal quality across devices, provide assets for various scales/DPI using one of the supported naming conventions.