Support all .NET Framework versions?

Investigate whether we should support all framework versions. Lets see how Newtonsoft.Json is supporting different versions.

For more on specifically .NET Core 3:

• Migrating a Sample WPF App to .NET Core 3 (Part 1)
• Migrating a Sample WPF App to .NET Core 3 (Part 2)

[FantasticFiasco]

@virzak I’ve hacked up a pre-release preview of the .NET Core 3.0 support, you can find it here on nuget.org.

For now I’m satisfied. When .NET Core 3.0 finally ships we’ll be able to let MvvmDialogs support it.

Best of lucks with validating your own application for .NET Core 3.0 support!

[FantasticFiasco]

All dialogs in my biggest application that uses this library work right out of the box with the latest beta.

Perfect, then I’ll start the process of releasing an official version.

I can make a separate issue with suggestions over the weekend if you’d like.

I would definitely like that. When creating the new .NET Core samples, I noted that the can-execute function wasn’t triggered as it does in .NET Framework. Or I made a mistake when I copied the samples and migrated them to .NET Core. Whatever it is, I am eager for your contribution. Thank you very much for your support!

Recently I replaced SimpleIoc with Microsoft.Extensions.DependencyInjection since it plays better with Polly (Microsoft.Extensions.Http.Polly) and EF Core.

I’ll look into that IoC container. I opted to chose sample dependencies that would be familiar to new WPF developers. I’ll look into the popularity of Microsoft.Extensions.DependencyInjection. If it gains traction over SimpleIoc I’ll have no problem doing the switch.