Skip to content

Move primitive types into their own nuget package #6687

@AdmiralSnyder

Description

@AdmiralSnyder

Primitives, like System.Windows.Point should be moved into a standalone Nuget package. They shouldn't be tied to WPF.
System.Drawing.Primities exists as a reference point. This would allow usage outside WPF.

That way, it's possible to reference them from libraries without having to put UseWPF into the .csproj files (keeping them small, as e.g. test projects testing the algorithms apart form their UI implementation should be)

Activity

changed the title [-]Move primitive types into their own System.Windows.Primitives nuget package[/-] [+]Move primitive types into their own nuget package[/+] on Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @SamBent@lindexi@AdmiralSnyder@pchaurasia14

      Issue actions

        Move primitive types into their own nuget package · Issue #6687 · dotnet/wpf