-
Notifications
You must be signed in to change notification settings - Fork 310
.NET Core Support #88
Comments
@mysteryx93 I believe you get .NET core support from the MvvmLightLibsStd10 (.NET Standard) package, however, it hasn't been updated since 2018 so might not give you the functionality you might like for WPF. |
Ah I see. Only problem is that GalaSoft.MvvmLight.CommandWpf won't be supported. Or keep it with the .NET Framework version; it's working but it's just showing the warnings. Also the code snippets plugin was never updated for Visual Studio 2019. Is there anyone still maintaining MvvmLight? |
Until we get any official statement from Laurent, you could always try to (look for a) fork. Another option is to try a similar library like Prism, which currently supports Wpf for .NETCoreApps |
.Net Core support would be great! |
I don't think there has been any official statement on whether MvvmLight is no longer going to be maintained. There has been a bit of effort to breathe new life into MvvmLight through building a new MVVM framework within the Windows Community Toolkit. The umbrella for this says Windows but don't worry. The MVVM Toolkit there which was inspired by the MvvmLight toolkit is platform agnostic. |
Sounds like an awesome initiative! I've looked at the other MVVM frameworks and I didn't find the extra features really useful for my specific needs. I prefer it does a basic job well. A well-supported rewrite with better performance would be a double-plus! |
Figured I'd follow-up here and say that we shipped our 7.0 version last month which includes the new MVVM Toolkit. You can find the notes on migrating from MVVM Light here: https://docs.microsoft.com/en-us/windows/communitytoolkit/mvvm/migratingfrommvvmlight and samples here: https://aka.ms/mvvmtoolkit/samples. |
Does that work with WPF too? |
@luetm yes, the MVVM Toolkit is based on .NET Standard and works with WPF, UWP, Xamarin, Uno, MAUI, WinUI 3, etc... |
When I add MvvmLight to a .NET Core project, I get this error
Has it been updated to work with .NET Core?
The text was updated successfully, but these errors were encountered: