Skip to content
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

Migration to Microsoft.Xaml.Behaviors.Wpf #3

Merged
merged 1 commit into from
Oct 11, 2019
Merged

Migration to Microsoft.Xaml.Behaviors.Wpf #3

merged 1 commit into from
Oct 11, 2019

Conversation

God-damnit-all
Copy link

Microsoft.Expression.Interactions is effectively deprecated with the open source Microsoft.Xaml.Behaviors.Wpf library taking its place.

A migration guide was published here: https://devblogs.microsoft.com/dotnet/open-sourcing-xaml-behaviors-for-wpf/

@trigger-segfault
Copy link
Owner

Thank you. I appreciate the full explanation of the new package and link to the simple migration guide. Definitely great news to hear, and I fully welcome less headaches with those two dlls from now on. 🎉

The only thing to keep an eye on is MvvmLight, which still references and includes System.Windows.Interactivity.dll in the build output. I'll just add it as a local project and fix the reference myself.

@trigger-segfault trigger-segfault merged commit 06be4cc into trigger-segfault:master Oct 11, 2019
@God-damnit-all
Copy link
Author

God-damnit-all commented Oct 12, 2019

That reminds me. you should also update TriggersTools.Build.BuildTime. That fixes the issue of TriggersTools.Build.BuildTime.dll being required to launch the program. Might as well update the CopyrightYear one too while you're at it.

@God-damnit-all God-damnit-all deleted the microsoft-xaml-behaviors branch October 26, 2019 21:00
@God-damnit-all
Copy link
Author

God-damnit-all commented Oct 26, 2019

Is MvvmLight possibly replaceable with something else? I was looking at the github for it and it seems like it's dead in the water. There's a lot of fleshed out PRs for it open that are just being flat out ignored.

I recommend merging this into your local project, by the way: lbugnion/mvvmlight#72

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants