Blog Post

Modern Work App Consult Blog
5 MIN READ

Using XAML Islands on Windows 10 19H1: fixing the "Catastrophic failure" exception

Matteo Pagani's avatar
Matteo Pagani
Icon for Microsoft rankMicrosoft
Mar 18, 2019
As you probably know, the AppConsult team has a strong focus on Windows app modernization. XAML Islands is one of the main technologies we're working with and with my buddy Sebastien Bovo we have del...
Updated Mar 19, 2019
Version 2.0
Matteo Pagani's avatar
Matteo Pagani
Icon for Microsoft rankMicrosoft
Feb 07, 2020

Hello Eric,

here is my feedback to your questions:

 

  1.  Yes, that's correct. The app manifest is an application concept, not a user control one. The user control will leverage the minimum and maximum version that you have specified for the main application.
  2. This blog post has been written before Windows 10 1903 was officially released. As such, the build number in the manifest was the most recent one related to Windows 1903 available at that time. Now that Windows 10 1903 is out, you can safely use the final build number, which is 18632. You don't have to increase it when new Windows 10 versions are released, you can stick to 18362 since it's the first public Windows 10 version to offer full support for XAML Islands.
  3. The error you are seeing isn't an error, but a requirement to specify the minimum OS version since version earlier than Windows 10 1903 don't offer XAML Islands support. Setting the minimum supported Windows 10 version (either via manifest or MSIX packaging) will always be a requirement. Things eventually might change with the release of WinUI 3.0, which will offer XAML Islands supports to older versions of Windows 10.

I hope it helps!