Publish System.Xaml as a separate nuget package.

[kekekeks]

There is a lot of code in production that uses System.Xaml separetely from WPF on server-side for purposes that aren't related to UI in any way, shape or form.
It's worth as a separate package and will be useful right now even without .NET Core 3.0 and working WPF.
I believe it could be shipped for netstandard2.0 to make it useful in .NET Standard libraries.

[kekekeks]

#51

[karelz]

Just FYI: Having System.Xaml as separate package (while it is part of Desktop UI shared framework shipping in the .NET Core platform) brings a set of non-trivial challenges (CoreFX repo had plenty of good & bad experience with them over last few years).
CoreFX team and WPF team will work closely together to fully understand all the challenges and additional costs associated with them. That will help us make the best decision if/when/how best to address this ask.

[taori]

I originally thought this is what was supposed to happen here, but since wpf is no open sources i guess that's a different site.

[WinInsider]

This has been an ask for long time, by many... Please do consider System.Xaml target .netstandard 2.0

[dotMorten]

There is a lot of code in production that uses System.Xaml separetely from WPF on server-side for purposes that aren't related to UI in any way, shape or form.

I'm curious if someone could list a set of detailed real-world scenarios for this. It might help sell the team on it.

[ewinnington]

Workflow foundation is an example of non-UI Xaml usage of system.xaml. It is a critical component to allow runtime workflows.

[kekekeks]

@dotMorten
Mostly custom workflow engines.
There is also Workflow Foundation open-source attempt: https://github.com/dmetzgar/corewf that would greatly benefit from having System.Xaml as a separate package.

[Kation]

For now Net Core 3.0 was released.
Is there any information about this issues?