Prism.DependencyObjectExtensions.CheckAccess unable to find DispatcherQueue property

[sigmarsson]

Please take a quick look at this issue to judge if it is a WinUI / Uno error or any API has changed, which is not yet harmonized. Thanks. It had worked prior to an update was made to <PackageReference Include="Microsoft.ProjectReunion" Version="0.8.1" />

[sigmarsson]

WinUI API has changed.

"In Reunion 0.8 DispatcherQueue moved from the Microsoft.System to the Microsoft.UI.Dispatching namespace."

[brianlagunas]

yeah, that will need to be done. @dansiegel is the owner of all things CI. I'll let him handle that when he recovers from his surgery.

[sigmarsson]

Merci.

[sigmarsson]

@brianlagunas , maybe could you please roll out a pre nuget inclusive this PR ?

[sigmarsson]

@brianlagunas , could you please tell how to forge a nuget for myself out of my dev branch ?

[dansiegel]

any time we merge to master a package is published to Sponsor Connect. This is only available to those who are active GitHub sponsors of either @brianlagunas or myself. Note that I'll take a look at the CI issue probably next week as I'm still recovering from surgery.

[crogeniks]

When can we expect this fix to publicly available? With WinUI dropping 1.0 I want to explore prism and compare to other frameworks, but this issue is blocking my exploration of Prism.

[sigmarsson]

Yeah it is strange that no1 of the WinUI community intends to incorporate Prism into their WinUI application. For (almost) a year ?

[brianlagunas]

Seems no one really cares enough about WinUI and Prism to make the effort. The community has spoken.

[crogeniks]

I don't know about spoken. The root cause was fixes by a member of the community. The PR was approved and merged back in august. In December, no public NuGet version with the fix was released.

I tried, although yes not very hard, no just compile Prism and see if it fits my needs. I didn't and waited for a NuGet update.

It has now been 10 months with no update on public NuGet update. I personally just moved on and decided to try another framework.

I totally understand that the maintainers of Prism are doing this as a side thing. I do not nor will never expect quick updates for free. I do believe the Sponsor connect is a good thing for the project. But at a certain point, when the general community is left out of all updates.. 🤷‍♂️

[edoust]

I used a custom build of Prism compiled for Uno/WinUI for a while, but then removed it, since IMO it doesn't offer any benefit anymore in the Uno/WinUI scenario. I now use what CommunityToolkit offers and further trimmed down the app so it runs cross-platform incl. with Blazor

Could you point out which parts of Prism you would like to use? Just curious how others see this issue

[sigmarsson]

@edoust i.e. : RegionAdapterBase<T>

[sigmarsson]

Hi Brian. blunt but still find it spooky because should we aggregate the WinUI+Uno communites, there must be more individuals than just me.
Perhaps the majority deserted because many controls related issues have not been stabilized for a long time ? for exapmple - ContentDialog. My project bogged down because XamDataChart is still in alpha, XamDockManager isn't even visible on the horizon, Prism isn't compiling due to this one. So IG invests primarily in low-code solutions and/or Angular, I do not know but hardly believe that commercial grade products are competitive without those controls. (for which I personaly would be paying)

[brianlagunas]

There is no mass adoption of WinUI by the market. There is no driving force, commercial or otherwise, that would encourage us to focus on, or even care about WinUI right now. The majority of the current market is web (Blazor, Angular, React, etc).

[sigmarsson]

Uno team, will make up the control's repertoire and furnish the Chart control for WinUI desktop. Would it be possible the community obtains a patched Prism for Uno like 8.1.98, just containing this patch, nothing else?