XAML parsing failed - running on Windows Server 2019

Question

We are trying to deploy our application on a VM running Windows Server 2019 and receiving the error below anytime an SfDataGrid is included in the XAML.

The packaged app runs on Win10 and Win11, but fails on Windows Server 2019 OS build 17763.4645.

The documentation says SyncFusion should work on anything > 17763 but I'm curious if there is a specific version that changes at. I've tested with grid version 21.1.35 and 22.1.34

Please let me know if you need any more info or have guidance on this issue.

Error:

2023-07-26 14:22.52.407 [ERROR] XAML parsing failed.

2023-07-26 14:22.52.443 [ERROR] at WinRT.ExceptionHelpers.<ThrowExceptionForHR>g__Throw|20_0(Int32 hr)

at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.LoadComponent(IObjectReference _obj, Object component, Uri resourceLocator, ComponentResourceLocation componentResourceLocation)

at PlanoFX.App.Views.Pages.UsersPage..ctor() in C:\source\PlanoFX.V2\Source\PlanoFX\PlanoFX.App\Views\Pages\UsersPage.xaml.cs:line 34

at PlanoFX.App.PlanoFX_App_XamlTypeInfo.XamlTypeInfoProvider.Activate_441_UsersPage() in C:\source\PlanoFX.V2\Source\PlanoFX\PlanoFX.App\obj\x64\Release\net7.0-windows10.0.19041.0\win10-x64\XamlTypeInfo.g.cs:line 1429

at ABI.Microsoft.UI.Xaml.Markup.IXamlType.Do_Abi_ActivateInstance_13(IntPtr thisPtr, IntPtr* result)

--- End of stack trace from previous location ---

at WinRT.ExceptionHelpers.<ThrowExceptionForHR>g__Throw|20_0(Int32 hr)

at ABI.Microsoft.UI.Xaml.Controls.INavigateMethods.Navigate(IObjectReference _obj, Type sourcePageType)

at PlanoFX.App.Views.MainNavView.NavigationView_SelectionChanged(NavigationView sender, NavigationViewSelectionChangedEventArgs args) in C:\source\PlanoFX.V2\Source\PlanoFX\PlanoFX.App\Views\MainNavView.xaml.cs:line 186

at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)

at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.<Post>b__0()

Chidanand Murugaiah · Answer

Hi Javier,We are currently analyzing the issue with the exact OS
version (Windows Server 2019) mentioned in the query. We need some time to
validate the reported scenario and provide an update on or before July 31,
2023.Additionally, we need some more information from your
side. 
 Did you face this issue only with
     the DataGrid control?
 Please share you Visual Studio
     version also.
Regards,Chidanand M

Javier Escajeda · Answer

- Currently the DataGrid is the only issue I'm aware of, but can test other controls and report my findings.- Visual Studio 2022 CurrentAdditional info:net7.0-windows10.0.17763.010.0.17763.010.0.17763.0Running / publishing as x64Publish profile below: FileSystem x64 win10-x64 bin\\win10-x64\publish\ true False false Release net7.0-windows10.0.19041.0 false true

Chidanand Murugaiah · Answer

Hi Javier Escajeda, Thank you for
providing the information we requested. As we mentioned earlier, we need time
to valid your reported scenario and provide an update on or before July 31,
2023. We appreciate your
patience until then. Regards, Chidanand M.

Chidanand Murugaiah · Answer

Hi Javier Escajeda,Based on the provided information, we have analyzed the issue in the Windows Server 2019 version. We faced some difficulties with the particular Target Framework version 'net7.0-windows10.0.17763.0' when trying to deploy SfDataGrid.However, we were able to overcome the issue by using the target framework as 'net7.0-windows10.0.19041.0' in the same OS version.Please refer to the below code snippet: net7.0-windows10.0.19041.0 10.0.17763.0 If you need any further assistance, feel free to contact us.Regards,Chidanand M.Attachment: Reference_Video_7b00e928.zip