Skip to content

WPF specific skills? #24

Open
Open

Description

I see the set of sub skills and detailed guidance for Winforms - do we need to have the same for WPF as well?

Activity

  1. mikadumont commented on Aug 25, 2026

    @mikadumont
    Contributor

    Hi Peter Smulovics (@psmulovics) thanks for providing this feedback! Are there specific scenarios for WPF that you would like support for?

  2. psmulovics commented on Aug 25, 2026

    @psmulovics
    Author

    It is a list of items - building-wpf-applications, managing-wpf-xaml-designer-code (no x:class mismatch, merged resources, clean builds, etc), managing-wpf-data-binding (missing INPCs, bindinglists, null/empty states, binding path diagnostics, etc), managing-wpf-mvvm (proper command migration with canexecute, UX integration, testability, etc), managing-wpf-async-apis (invoke from worker/ui contexts, .result/.wait handling in ui call chains, cancellation tokens and exception flows, etc), managing-wpf-layout-and-dpi (to move from fixed position layouts to intent preserving layouts), managing-wpf-themes (dark/light, fluent, accent aware, high contrast, dialogs/popups, disabled/focused, proper 3rd party controls, etc), managing-wpf-resources-styles-templates, creating-wpf-custom-controls (pixel/visual baseline, resize, DPI, clipping, transforms, hit testing, redraw and animation perf, memory), managing-wpf-rendering, managing-wpf-items-and-virtualization, etc. Also, a bunch of scenarios, eg wpf-feature-adoption with all the needed bits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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