ravibpatel
Why is AutoUpdater.NET not implemented along the lines of MVVM?
Today I have made a WPF application autoupdatable using AutoUpdater.NET. I was impressed with its ease of use. But while I was implementing this functionality, I was wondering why AutoUpdater.NET is not developed along the lines of MVVM. I am more than happy to contribute my bit, if you have MVVM plans with AutoUpdater.Net.
@KoruNL I developed this library a long time ago with very basic functionality. Now it has more features so I think it will benefit using MVVM. That way other developers can migrate the user interface part to any UI Framework. I think MVVM will be very useful for version 2.0 with WPF forms. You can open pull request if you like to contribute.
@ravibpatel Can you outline what you want implemented (and left behind) in version 2.0?
@ravibpatel The target framework for AutoUpdater.NET is .NET 4 now. Should this be the case for version 2.0 as well or can we move up a bit?
@KoruNL I prefer sticking to 4.0. Although it works on version .NET 2.0 too but for version 2.0 we can ditch .NET 2.0 support.
@ravibpatel So we keep using BackgroundWorker instead of moving to async await.
@KoruNL I really like to move to async await but that will mean not supporting .net 4.0 which many developers still use.
I can't speak for others but .NET 4.0 is definitely out of circulation in my projects.
Any of my .NET Framework projects are either using .NET 4.6.1 or .NEET 4.7.1 . I think you can comfortably remove .NET 4.0 support for version 2.0 .
