Put this entire repo into Microsoft.UI.Xaml

[jamers99]

Since the open sourcing of Microsoft.UI.Xaml why not build this library into UWP?

[LocalJoost]

Agreed. Or, in the tradition of the Windev MVP DL +1 <http://www.9folders.com/>Joost van Schaik Windows Development MVP "The world as I envision it in my head is such a more interesting place"

…

________________________________ From: James Esh <notifications@github.com> Sent: Tuesday, December 11, 2018 22:22 To: Microsoft/XamlBehaviors Cc: Subscribed Subject: [Microsoft/XamlBehaviors] Put this entire repo into Microsoft.UI.Xaml (#147) Since the open sourcing of Microsoft.UI.Xaml<https://github.com/Microsoft/microsoft-ui-xaml> why not build this library into UWP? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#147>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD8Bn5EkNYEINzi1lqcKCEk1N2ZU_pnLks5u4CIAgaJpZM4ZOQ4n>.

[sonnemaf]

Agree , +1

[jupagose]

Agree , +1

[michael-hawker]

If not, there would still need to be a version to target WinUI 3 anyway, see POC PR #164.

Has anyone filed an issue yet on the WinUI repo about this proposal?

FYI @ryandemopoulos

[michael-hawker]

@brianlagunas @pedrolamas are you or others planning to still maintain this library? I think you were the last contacts I had. Just wanted to see if this was something you'd discussed or talked about with the WinUI team; especially now as WinUI 3 will be open sourced?

I think with the broad usage of Behaviors as part of XAML and having both C++ & C# support, having it be part of the platform itself would make sense.

@DVaughan I know we've been helping build the WinUI 3 packages, but the main branch CI still seems to be broken, is this something you can help fix? (also detailed here)

FYI @stmoy

[pedrolamas]

In terms of stability, I'd say this library is quite mature, hence why little to no changes have been pushed in the past few months (at least on the C# side which is what I work on). So personally, I've mostly been trying to reply to issues raised by other developers.

Having said that, it does make sense to me to make this part of the platform but as far as I know, no discussions have been had in that regard - but then again, I'm not an MVP anymore, so at this stage @brianlagunas might know more about this than I do!

[brianlagunas]

I'm in a similar boat as @pedrolamas. This is a mature library, and there aren't really any issues being submitted. I try to respond to issues as they come in. As far as working with the WinUI team, there has not been any communication with MS about that kind of effort. Keep in mind, this is a MS repo. @pedrolamas and myself just help out when we can, but have no control over where it lives, or the processes that govern it.

[Panda-Sharp]

Any news on this? would be really nice to have this in a more active repo, currently I see 4 PRs and 48 issues basically unanswered here :(

CC
microsoft/microsoft-ui-xaml#3813

[GuildOfCalamity]

Are there still plans to integrate this into Microsoft.UI.Xaml?
This should not have to be added as an additional NuGet to projects, as the functionality is sorely lacking in the base classes.

[mgoertz-msft]

@GuildOfCalamity Not up to my team unfortunately. Internal discussions never went anywhere and given that the public ask on the Microsoft.UI.Xaml side is several years old I would say the chance of them integrating this functionality is rather low.

[GuildOfCalamity]

@mgoertz-msft That's a shame. Well, thanks for the update.