Telerik UI for MAUI and MAUI preview 13

Thank you very much.

Do you already know when MAUI 0.6.0 is going to be released?

Please follow this ticket:

https://www.telerik.com/forums/move-to-maui-0-6-0

HI folks!

As Daniel stated, v0.5.0 was built with .NET MAUI preview13, there's just no way to use it with preview14. We're working hard to release v0.6.0 as soon as possible, which is built with preview14.

You can keep an eye on the Release History page or check in on Daniel's linked other forum thread (I'll post there when it's available).

Hi Arkady,

This is just the reality when working with preview SDKs and is par for the course, it is fully expected behavior. Please let me explain.

There is a strong warning from Microsoft to expect breaking changes for every single preview release of .NET MAUI. Thus, it is fully expected that a library built with preview13 will not work with preview14, and a library built with preview14 will not work RC1.

This should be easier now that we're in Release Candidate territory, meaning that going from RC1 to RC2 will hopefully have no breaking changes, but even that is not guaranteed. We are building the library on top of RC1 right now and will have a new release soon.

Until v1.0.0 is available, please keep in mind the following facts in mind

• Expect breaking code changes every preview release
• Expect that packages are not backwards compatible with prior preview SDKs
• Do not expect production-ready code that you can publish (in fact, you cannot legally publish an app with UI for MAUI until it reaches v1.0)

We are getting close to .NET MAUI general availability release, but until then, I ask that you please understand this is how it goes when using preview technology and be patient in between releases. In the meantime, we continue to look forward to your feedback about specific features and API surface areas as we build out the UI for MAUI controls.

I'm ok with breaking code changes, my worry is because it is the same problem appearing again and again, for me it looks like you didnt fixed it properly... or whatever...

And now i just tried on Mac and there is also an issue but different, so is more understandable... something broken with new release, so i can rollback to preview 14 and use it, but with that Duplicate Entry one - i dont have any working release , so keep using preview 12 and telerik 0.4.0 !!!, because no more working combination of telerik 0.4.0, 0.5.0, 0.6.0 and preview 13, 14 or rc1 - it just same error every release, so here is why my patience is over!

Completely understandable! To clarify things, and hopefully add some sanity, here how the release numbers line up:

• .NET MAUI preview 12 <-> Telerik UI for MAUI 0.4.0
• .NET MAUI preview 13 <-> Telerik UI for MAUI 0.5.0
• .NET MAUI preview 14 <-> Telerik UI for MAUI 0.6.0
• .NET MAUI RC1 <-> Telerik UI for MAUI 0.7.0

We are close to finishing up UI for MAUI 0.7. We've already rebuilt the base on top of .NET MAUI RC1, handled all the breaking changes and are currently in the process of running all our tests to make sure there are no regressions.

I'd expect that we'll be able to release it tomorrow, assuming no breaking changes, but I don't want to promise that you because it's still possible that it would need to get to get delayed a day or two due to a regression (which happened last time).

Rest assured that we want you to have 0.7.0 as soon as possible. I will personally come back to this thread and let you know when its available.

If you cannot wait, then you'll want to use .NET MAUI preview14 and Telerik UI for MAUI 0.6.0 (though it is rather difficult to downgrade .NET MAUI after it has been updated to the next preview/RC).

Pro Tip

As far as the Duplicate entry is specific to Windows projects. When you do eventually migrate to RC1, please carefully read the .NET MAUI Migration release notes as it has important information about changes and stuff you need to remove from your csproj.

My best trick for this is do not use a csproj that was generated for a previous preview. There are changes in the SDK that may require different setup in the csproj and sometimes importantly a different project structure overall (especially if you created that project before preview13). So, I recommend that you generate a new blank MAUI project with the same namespace as your existing project (File > New Project > .NET MAUI), then copy your code files into the new project.

At a minimum, you should at least replicate the new csproj contents in the old project's csproj. This particularly will fix Windows dependency build issues because RC1 no longer requires Windows NuGet packages.

so once you moved to version 7

We need to update vs to 17 preview 3

Create new project with same namespace 

And copy the files from old project to new one.

Correct, once 0.7.0 is available,  you can then update to .NET MAUI RC1 by updating VS 2022 Preview (to v17.2.0 Preview 3.0). Updating VS will also update .NET MAUI for you at the same time.

Daniel, as far as your projects go,  I'm not sure if you need a new csproj. The demos you have been sending me are okay, but you still need to remove the Windows dependencies manually. I'm not sure if your real project needs to be updated to RC1 standards or not. You can incrementally test

• If it works with RC1 after you remove the Windows dependencies from the csproj, then you're good.
• If it doesn't work, then a whole-project-transplant might be needed.

After RC1, these kinds of things should no longer be needed, but there's still a very small chance. After 1.0, then you're stable.

HI Folks, Telerik UI for MAUI 0.7.0 is now available.  You can see the release notes here => Telerik UI for MAUI - Telerik UI for .NET MAUI Preview(version 0.7.0)

Remember that this is built for .NET MAUI RC1, so do not update your project's Telerik dependencies until you've updated your SDK to RC1. You will want to carefully review Microsoft's guidance in their ongoing Migration guides => Migrating to RC1 · dotnet/maui Wiki (github.com) 

Make sure you do a full clean and rebuild, otherwise VS isn't going to properly pull in everything it needs because it caches packages and assemblies for faster builds.

I recommend closing Visual Studio, then deleting the MAUI project's bin and obj folder. After that's gone, you can go back into VS and do a Rebuild.

The same problem happens to me every time I update a package and forget to clean it.

I found the cause, somehow you components interfere with CommunityToolkit.Maui (see my screenshot above). This time it helped to upgrade CommunityToolkit.Maui to RC3. Now can build project!

Yes, Daniel, it is ready, you can take the following steps:

1. - Update VS 2022 Preview (to 17.3 Preview 1.0)
2. - Update .NET MAUI to RC3 (open Powershell and run 'dotnet workload install maui --ignore-failed-sources')
3. - Update your project to use Telerik UI for MAUI to v 0.9.0
4. - Clean and Rebuild the project

Hi,

In step 3 not to open new project and copy the files 

From RC2 to  RC3?  

I don't have shell in my project?

I'm not sure what Shell has to do with this. I can't guide you on code migration, this is specific to your project on whether you need to or not.

I do recommend, to at least, create a new RC3 project and look at the changes there. Microsoft switched to using MSBUILD identifiers for platform conditions:

A note about Tizen. Microsoft added a platform folder for Samsung's Tizen framework in the RC3 project template. Telerik UI for MAUI doesn't have support for Tizen. So if you do create a new project to use, you can delete that platform folder/target from your project.