Alexandre Zollinger Chohfi
Alexandre Zollinger Chohfi
I don't think this is related to @Nirmal4G's work. UWP never supported AnyCPU as a target. You need to select a specific architecture. That is by design. Is the underlying...
Hello @LeoCarriere , thanks for the report. Unfortunately, this is a known issue, as the CameraPreview control depends on MediaPlayerElement, which is still not supported on WinUI3. Not sure if...
I believe this is the "Resources" xml tag inside the file, not the file name itself. I'm not sure how the resource manager works on regards to bundling things in...
I thought that the compilation process bundled everything into a resources.pri file, and that is why it had to start with "Resources/*". Maybe @RealTommyKlein can clarify.
I recommend this presentation on Channel 9: https://channel9.msdn.com/Shows/On-NET/Supporting-Windows-Forms-and-WPF-in-NET-Core-3
No concerns.
This affects the HighPerformance package, as well as the Notifications one. I'm mostly worried about the notifications, as we support older targets and need to keep them working: https://github.com/CommunityToolkit/WindowsCommunityToolkit/blob/main/Microsoft.Toolkit.Uwp.Notifications/Microsoft.Toolkit.Uwp.Notifications.csproj#L4 I...
Sounds great! Is there a ball park date for when do you think the NCT bits will be moved?
This is an activation issue. Which DLL does your app.manifest registers that type in? Is this a clean build? Try deleting bin/obj and rebuilding it.
Oh, my bad. I looked into this better and it seems like a Win2D issue. @getrou / @iablaauw-MS