Skip to content

Consider shipping System.Xaml as a separate netstandard package #4140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ryalanms opened this issue Feb 5, 2021 · 5 comments
Closed

Consider shipping System.Xaml as a separate netstandard package #4140

ryalanms opened this issue Feb 5, 2021 · 5 comments

Comments

@ryalanms
Copy link
Member

ryalanms commented Feb 5, 2021

System.Xaml can be used independently of WPF, but consuming System.Xaml requires building with the Windows-specific net6.0-windows target framework. Consider shipping System.Xaml as a separate netstandard package that can be built without the Windows-specific TFM.

@lindexi
Copy link
Member

lindexi commented Feb 6, 2021

Yeah, and I made it as a separate package in https://github.com/lindexi/lindexi_gd/tree/master/System.Xaml

@ryalanms ryalanms added this to the Future milestone Feb 11, 2021
@lindexi
Copy link
Member

lindexi commented Mar 8, 2021

@ryalanms Because System.Xaml depends on System.Windows.Extensions, I cannot change it to netstandard. See #4252

@lindexi
Copy link
Member

lindexi commented Jul 3, 2021

See #3543

@AArnott
Copy link

AArnott commented Sep 19, 2022

Looks like a dupe of #46

@pchaurasia14
Copy link
Member

Closing as duplicate.

@ghost ghost removed this from the Future milestone Aug 30, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Sep 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants