WPF - .NET 5 Support & New Designer Features

Upgrading my application to use DevExpress 20.2.3 wpf components, fails compilation in Visual Studio 16.8.

Some weird messages are shown like some Microsoft assemblies expected of version 4.6; but found 4.5. I have no clue of what these messages are. When I am upgrading the DevExpress components version, why should I get messages about Microsoft assemblies?

The whole thing is confusing, and I am frustrated.

- Satya Kolachina

Hi Alex,

I want to share here my observation and how I fixed the problem. May be it will help your team one way or the other.

When I first installed DevExpress components version 20.2.3, after upgrading Visual studio to version 16.8, and tried compiling my application, I noticed that Visual Studio was complaining that some of .NET's original libraries were itself downgraded to earlier versions. This was completely confusing to me and I could not understand how it happened.

Then I tested on a different machine with identical Visual Studio installation. But, this time I did not install DevExpress components at all; I pulled only the relevant packages through NuGet package manager, and added them to my solution. 

This time it compiled error-free. I strongly believe that installing the DevExpress components locally onto the machine has done something wrong to my Visual Studio configuration. On that prior machine, I reinstalled Windows 10, followed by Visual Studio and just pulled DevExpress components using Nuget package manager. I chose to reinstall windows 10, because I do not want a machine with improper .NET packages sitting in the C: drive, which cannot be cleaned-up or repaired easily.

Now I am seriously scared to install DevExpress components locally onto my computer, as I am not ready to redo all the installations.

I want to hear from DevExpress that the installation of DevExpress WPF components locally on the computer is safe; until then I prefer the NuGet package manager approach.

Regards,

Satya S Kolachina

Hello,

I have been trying to switch from classical Winforms (.Net Framework) to WPF and willing to use .Net5 SDK for some time. I start to get use to MVVM pattern now,its quite fun but losing the simplicty of using your components on a .Net Framework project is not there. I wouldn't like to read all your documentation for every piece of XAML work, before I used to let it done by your designer tools. Now I have to use a dummy .Net Framework project to let DX designers to generate XAML code and to apply some other templates. I think you should upgrade your wizards to support EFCore with MVVM pattern too.

Thanks and good luck.

Hello,

Again me :)

Any chance WPF Designer Extensions will be available

for .Net Core 5 projects any time soon?

I wonder what everyone else doing, coding everything in XAML?

Thanks,