Hi Bill, 

v12.1 s over 10 years old. So there's no way that version could possibly be compatible with Net 5, which was only released recently. 

The latest version of the control are available for .Net 5, though. I'm not sure exactly what version we started supported .Net 5 in. I think it was 20.2 or maybe 21.1. 

Hi Mike,
According to the release notes for v12.1  "All included assemblies have been built against Microsoft .NET Framework Version 4.0. You must have this version of the framework installed for the product to work."
How can these be .NET 5 compatible if they require the .NET Framework Version 4? 

When do you expect to release a version of your controls built on, and fully compatible with .NET 5, that don't require the .NET Framework?  

Hi Joe, 

I'm confused. The issue reported here was already fixed a while ago, as I explained in my last reply. But this is regarding Windows Forms - it's nothing to do with Blazor. 

Any update to this? .NET 5 now requires VS2019 16.8 or higher so my futile attempt to downgrade my VS in order to use a product we pay for was in vain. I thought trying to use ignite UI for Blazor was a horrible experience, at least I could get it to work. Well, I guess I did have to revert to the 2020 version of ignite UI for Blazor so this seems par for the course. 

Hi Geoff, 

Pretty sure this is fixed in our latest bi-weekly build. Which means you can get it by checking the "Include prerelease" checkbox in the NuGet package manager in Visual Studio.