[Closed] Separate toolkit without depending on MAUI for .NET 6 native apps

[dimonovdd]

This discussion is related to issue #11 (Add from Xamarin.Essentials: Contacts, FilePicker, MediaPicker and WebAuthenticator)

I think: If we want to cut up Essentials, then we need to create a separate repository or nuget for these APIs without dependence on MAUI for using with .NET 6 native apps.

Also to avoid code duplication we need to make some things from Maui.Essentials public (Permissions.EnsureDeclared, IntermediateActivity and etc.)

We also need to think about: Which library will contributors be able to add new features? Toolkit or directly to Essentials?

[dimonovdd]

xamarin/Essentials#1757 is an example using MediaPicker from Xamarin.Essentials in native Xamarin applications without Xamarin.Forms

Developers also want to use Maui.Essentials and its features without Maui dotnet/maui#1779

[brminnick]

There are couple points to address here.

Code Duplication

There will not be any code duplication between .NET MAUI, Maui Essentials and the Maui Community Toolkit. Both .NET MAUI and Maui Essentials have granted InternalsVisibleTo to CommunityToolkit.Maui: dotnet/maui#1970

Required Use of Maui

None of the new features being added in #11 require the use of .NET MAUI. I.e. You will still be able to use FilePicker, Contacts, MediaPicker and WebAuthenticator in your native .NET iOS (aka Xamarin.iOS) and native .NET Android (aka Xamarin.Android) apps.

Creating Essentials.Toolkit

We do not currently have plans to create a new toolkit for these APIs.

[dimonovdd]

this ToolKit use property <UseMaui>true</UseMaui>. This can increase the build time and add complexity to the linker. As I wrote above there are those who want to use only <UseMauiEssentials>true</UseMauiEssentials>

[pictos]

This can increase the build time

We need to measure that and see if the build time will be an issue.

and add complexity to the linker

Why? The XCT is linker safer by default and we want to keep this behavior here. The code that we will bring from Essentials are all static so that will be very easy to work with linker

[dimonovdd]

Why then divide Maui into parts, if using everything is not different from using only Maui.Essentials?
<UseMaui> <UseMauiEssentials> <UseMauiAssets>
Don't these properties have different meanings?

[dimonovdd]

I am not alone, other developers also do not like unnecessary dependencies
dotnet/maui#2337

[dimonovdd]

These features will remain in Maui.Essentials

link

[brminnick]

Closing Discussion now that #11 is closed

[CliffAgius]

Closed as answered.