Hi Nathaniel,

I just wanted to follow up with you in this thread to share the tracking item for this issue => Duplicate resource error with latest version of MAUI & Visual Studio 2022 17.3.0 Preview 2.0 (telerik.com)

Please go there and click the "Follow" button. This will subscribe you to any posts or status changes for that tracking item. I have spoken to the dev team and they are indeed working on it. I will post an update to that item when the update is available.

Thank you for your understanding and patience while we work on getting a Telerik UI for MAUI update ready.

Regards,
Lance | Manager Technical Support
Progress Telerik

Hello Nathaniel,

I assume you're getting the following errors:

1>WINAPPSDKGENERATEPROJECTPRIFILE : error : PRI175: 0x80073b0f - Processing Resources failed with error: Duplicate Entry.
1>WINAPPSDKGENERATEPROJECTPRIFILE : error : PRI222: 0x80073b0f - Unspecified error occurred.

These errors happen when there is a mismatch between Windows SDKs. The problem appears to be because Microsoft released an update to VS 2022 Preview today which also included an update to the .NET MAUI workloads. If .NET MAUI's Windows components are being built with the latest Windows App SDK, then this explains the errors. This will breaks anyone who had built windows components on top of .NET MAUI before today.

Ultimately, I suspect is happening because of the parallel development of the WinUI3 and Windows App SDK. The latest .NET MAUI release targets Windows App SDK 1.1, which came out a couple days after .NET MAUI was pushed to go "GA" for Microsoft Build. We need to also meet these minimum SDK requirements, but I need to leave this determination up to our development team.

The Telerik UI for MAUI team is working on this and will release an update as soon as possible (also requires unit testing and QA pass). The one advantage to this is that the update should also contain other improvements we've been working on since Microsoft Build.

I will come back here and update you with any details I get from the dev team.

Side Note & Pro-Tip

To answer your main concern, although MAUI is considered "GA", it doesn't mean they cannot introduce changes when the .NET MAUI workloads are updated.

I can understand an empathize with your frustration, the "seems like every update breaks my app" feeling. There are a lot of moving parts in a.NET MAUI situation that must all align, or at least have a "min SDK" setup. Now that Windows App SDK 1.1 is available and the .NET MAUI team isn't looking for more Windows platform features, this should be stable for a while.

However, it's best to take the stance that major updates come with the possibility of breaking changes, especially with  .NET MAUI workloads because they're nearly impossible to revert. So, my 'pro tip' for you is that you do not update your main development machine as soon as there's a known update available.

First, test the update in a temporary or throwaway environment (I use a Hyper-V VM for this, super-quick to setup) . If there are breaking changes, you'll be able to keep developing on your main machine until we have an updated package a day or two later.

Regards,
Lance | Manager Technical Support
Progress Telerik

Hi Mike,

That's good news, yes VS Preview doesn't know how to handle conditioned ItemGroups.

Though I'm curious why you still have ItemGroups with conditions. There should be no more ItemGroup with a condition for Windows as the WinAppSDK is included in MAUI (this was a change in RC2 or maybe RC1?). Additionally, Microsoft changed the way they calculate the platform conditions... the Condition="..." statement now uses an MSBuild flag.

I recommend quickly creating a throwaway RC3 project using Microsoft's project template and see the differences between RC2/1.

*caveat - You may have a windows item group if you're doing custom platform-specific stuff with a newer WinAppSDK (like the preview for 1.1). That said, the Telerik.UI.for.MAUI package should never be in a conditioned group.

Regards,
Lance | Manager Technical Support
Progress Telerik

Hi Mike,

You can now download UI for MAUI v0.9.0 from your downloads page or do an upgrade from our NuGet server.

Important: Clean the solution before attempting to build the project, otherwise VS2022 will use caches assemblies and you'll see the same error. I personally recommend deleting the bin and obj folders of the MAUI project entirely (you may need to close VS2022 if you cannot delete the bin because it can sometimes lock a file)

Regards,
Lance | Manager Technical Support
Progress Telerik

Hi Mike,

I wanted to quickly follow up to let you know that I've done some tests with our early 0.9.0 builds on RC3 and it's working good. So, assuming we've committed all our latest changes and no new gremlins popup to bonk the QA testers on the head, I imagine this should get released a little bit faster than our other prereleases have been able to.

As I promised previously, I will come back here and update you when 0.9.0 is available.

Regards,
Lance | Manager Technical Support
Progress Telerik

Hello Mike,

RC3 was released yesterday, we do not yet have a public version of Telerik UI for MAUI that has been compiled with/for RC3. As you mentioned, the current preview release, 0.8.0, was created when RC2 was available.

As with all prereleases, we cannot promise an exact date of the next update. On average, since preview12, this has been taking about 2-3 business days... because we not only need to recompile the builds, but also include the new component changes and re-run all automated and manual QA tests.

When our next version is released, which is expected to be 0.9.0, you'll be able to build it on top of RC3 (unless Microsoft releases breaking changes in an RC4 before then and we weren't able to rebuild on top of that).

I will come back here and update this thread when the next version of UI for MAUI is available. Thank you for your patience and understanding.

Regards,
Lance | Manager Technical Support
Progress Telerik