Skip to content

Petition to change the NET6 WinUI project structure #7434

@mikernet

Description

@mikernet

I think the multitargeted Mobile project is far less ideal than how it was set up previously with individual projects for each platform. This makes it harder to unload a subset of those projects while you are only working on some/one at the time and I'm not a fan of the organization of having subfolders for each platform. That doesn't seem to be an improvement over having that organized into individual projects.

Is there a benefit to doing it this way? Is there even a way I can only build a subset of the targets in the mobile project without editing the .csproj file each time? I don't want to wait for iOS builds if I'm currently testing the Android project.

Adding package references to a subset of the targets (or different package versions for different targets) also becomes much more cumbersome as far as I can tell.

Metadata

Metadata

Assignees

No one assigned

    Labels

    difficulty/tbdCategorizes an issue for which the difficulty level needs to be defined.kind/enhancementNew feature or requesttriage/untriagedIndicates an issue requires triaging or verification

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions