Skip to content

Example structure is vastly different to visual studio 2022 templates, without explanation #17

@minfrin

Description

@minfrin

When building a new winui3 app template from visual studio, the structure of the template and this example application are structured nothing like each other.

In the most recent template, the App class instantiates a MainWIndow, with Window as the root XAML element.

In this example project, the App class jumps through a lot of unexplained hoops to wrap a MainPage, with Page as the root XAML element. Why?

The Page element is associated with a Page.Resources element, which is tightly woven into the example. The Window element has no corresponding Window.Resource element, nothing like this exists. Why?

With WinUI3 data binding completely undocumented for C++, we have to rely on examples to make up for it, but I've found zero examples that show any kind of meaningful data binding (binding a single string is useless as an example, that it of no use to anyone).

Are there examples to replace this one?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions