Telerik MAUI is not compatible with net6.0

Hey Antoan,

Thank you for quick feedback. I see what you mentioned, Actually we have another situation, We need a xUnitTest project for ClassLibrary(ProjectB), That is why we keep Net6.0 there. And based on that ProjectB's pages can't add Telerik component.  

I'm still struggling on how to figure out a solution to resolve it? 

Thanks

Allen

Hi Allen,

The net6.0-platform TFM comes with .NET 6 support implicitly, you shouldn't need to add net6.0 on top of it.

If you have another dependency that requires net6.0 be declared, then you have two options to move forward:

1. Contact the dependency's authors and request they add MAUI targets
2. Restructuring the library design so that you have one class library for only net6.0 code and a second one for MAUI targets

I personally would recommend option #2 because you shouldn't mix UI platform code with platform-agnostic code.

Hi Antoan, 

2.Restructuring the library design so that you have one class library for only net6.0 code and a second one for MAUI targets

We understand #2 is an alternate way , but if we have View(with telerik component) and ViewModel(VM) in the Projects and we want to unit test the VM then we have to separate VM to its own .net6 project ,  we don't want to separate VM from View in to 2  different projects.

Is there anyway we keep the View and VM in one project and still able to unit test VM?

1.Contact the dependency's authors and request they add MAUI targets

Sorry I did not get this, Are you saying we have to contact dependency's author for  Telerik.UI.for.MAUI.Trial 1.0.1 ?

Thanks,

Balaji

It sounds like the testing framework you're using is balking at the fact that the class library project doesn't have a separate net6.0 TFM.  This is what I meant about contacting that dependency author and asking them to add net6.0-android, net6.0-windows, net6.0-maccatalyst and/or net6.0-ios.

The bottom line is you cannot use UI code (Telerik UI for MAUI) in a non-UI, net6.0 only, class library. Telerik U for MAUI is dependent on the target platform, so any project it is referenced in must define MAUI TFM when that is compiled. It is not a platform-agnostic component library that can be compiled in a platform-agnostic net6.0 only library.

We agree Telerik UI is not a platform-agnostic component library that can be compiled in a platform-agnostic net6.0.

But we have created UI libraries with MAUI UI controls which allows us to compile in net6.0 and it is consumed by application exe assembly which targets to specific platforms like net6.0-windows and net6.0-maccatalyst. We are not consuming this class libraries in .net6.0 application which can be issue.

Also if you create sample class library through MS MAUI project wizard they do add .net6.0 as target framework. 

<PropertyGroup>
<TargetFrameworks>net6.0;net6.0-android;net6.0-ios;net6.0-maccatalyst</TargetFrameworks>
<TargetFrameworks Condition="$([MSBuild]::IsOSPlatform('windows'))">$(TargetFrameworks);net6.0-windows10.0.19041.0</TargetFrameworks>

If this not possible in telerik libraries then we will have to change our test project to have different targets.

Hi Allen,

The problem is that class library project is trying to compile a dependency that only supports .NET MAUI into an assembly that only targets the lowest common denominator net6.0. This is not possible because net6.0 does not have any support for .NET MAUI  (remember, .NET MAUI is net6.0-ios/net6.0-android/etc)

I do understand what you're trying to do, the bottom line is we do not surface any assemblies that are compatible for only the net6.0 target because our code is only for .NET MAUI platforms. To simply say it; Telerik UI for MAUI is for .NET MAUI, not .NET 6.0

You could add some custom #if preprocessor statements inside your class library that will exclude the Telerik code when the target is only net6.0

For example:

#if WINDOWS10_0_17763_0_OR_GREATER
#elif MACCATALYST
#elif IOS
#elif ANDROID

// .NET MAUI compatible code can go in here (e.g., Telerik UI for MAUI)

#elif

// Your net6.0 only compatible code goes here

#endif

Note: If your class library doesn't have .NET MAUI preprocessor statements, you will need to manually add them. I do not have any tutorials that show you how to do it, but you could ask Microsoft: here: dotnet-maui - Microsoft Q&A (or here dotnet-csharp - Microsoft Q&A).

Hey Lance, 

I did follow your suggestion to manually add TFS into *Test. csproj,

it can build successfully, but can't run test case, and it also show me below error when I did a run. 

Thanks

Allen

Hello Allen,

Can you share a small demo with me that I can use to experiment with? Something like what you have in your first screenshot. I will use that to experiment with, I'll also use it to talk to our QA engineers and see what they might offer for suggestions.

Hi Allen, thank you for the effort in preparing the project.

I also wanted to share news that I've spoken with product owners and they are currently working on adding net6.0 TFM to our compiled assemblies so that it can be used in this scenario. I can't promise anything right now, but barring any serious blockers, you should be able to use your original combined setup in a future release.

For now, I'll see what I can do with the attached setup.

Hello Allen, unfortunately I was not able to figure out a way to get this to work. Therefore, I have created a Feature Request on your behalf => Add net6.0 TFM to support tests (telerik.com)

This will allow you to track the progress of the item and be notified when it is available. Please go there and click the ":Follow" button, I have already added an upvote for you.

Hi Lance,

we just checked this issue was fixed in Telerik UI for MAUI .2.3.0