How does this skill handle multiple views of the same data?

It uses a Service Layer as a factory to create multiple filtered or sorted IEnumerable instances from a single ObservableCollection source, allowing different UI components to see different slices of data.

Can I use this with Dependency Injection (DI)?

Yes, the skill provides patterns for defining service interfaces and registering them in standard .NET DI containers for constructor injection into ViewModels.

Does this approach require specific .NET versions?

While the examples use modern C# syntax, the architectural pattern is applicable to all versions of WPF on .NET Framework, .NET Core, and .NET 5+.

Why should I move CollectionView logic out of the ViewModel?

Moving it to a service layer ensures your ViewModel stays pure C# (BCL), making it more testable and preventing unwanted dependencies on WPF-specific assemblies like PresentationFramework.dll.

Does the UI still update automatically when the source data changes?

Yes, because the CollectionViewSource is bound to an ObservableCollection, any additions or removals in the source are automatically reflected in all views generated by the service.

WPF MVVM CollectionView Manager

Name: WPF MVVM CollectionView Manager
Author: christian289

bychristian289

•

学習とドキュメンテーション

Implements a service-layer approach to manage WPF CollectionViews while maintaining strict MVVM architectural principles.

This skill provides a standardized implementation pattern for handling WPF filtering, sorting, and grouping through a dedicated Service Layer. By encapsulating CollectionViewSource within services and exposing only BCL-compatible IEnumerable types to ViewModels, it ensures that your business logic remains completely independent of WPF-specific assemblies like WindowsBase or PresentationFramework. This approach improves testability, promotes code reusability across different views, and facilitates cleaner dependency injection in complex .NET desktop applications.

主な機能

01Service-based encapsulation of filtering, sorting, and grouping logic

02Dynamic view creation using the Factory pattern for multiple filtered views

03Strict MVVM separation by removing WPF assembly references from ViewModels

04Automatic synchronization between source collections and UI views

05Standardized assembly reference rules for clean architecture

066 GitHub stars

ユースケース

01Decoupling WPF applications to enable framework-independent unit testing

02Filtering a single data source with different criteria across multiple WPF views

03Implementing complex sorting and grouping logic without bloating the ViewModel

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add christian289/dotnet-with-claudecode managing-wpf-collectionview-mvvm

For use in Claude.ai and ChatGPT

Download Skill