Discussion on the incompatibility between the api service request hierarchy of maui and the winui3 project

[git102347501]

I am using Winui3 to develop a desktop application, and using MAUI to develop a mobile version, to practice the NET technology stack in the production project.

I found that the project template of Winui3 will separate {} Object} Core layer is used for MVVM's model service request, encapsulating page entities

The information retrieval service includes some local file operations, such as the file information CRUD used by FileService to specify the path.

Therefore, this layer will rely on some class libraries operated by local resources. His project is Net6.0. To avoid repetitive API code requests, I want to

It is said that the core layer of the winui3 project is uploaded to nuget and the MAUI service request is monitored. But actually, because the MAUI belongs to netstand2.0, it cannot

Apply the nuget package of NET6.0.

I want to know whether MAUI has other considerations for separate layering and encapsulation of service requests? Netstand 2.0 restricts the availability range of project references,

Compared with the project template of winui3, I think MAUI is not good enough in separating MVVM services.

[git102347501]