Hi Andrew,

It's been now twelve months since your post and there is still no progress on this. Ultimate UI for Windows Forms is still lacking a working designer view when using .Net Core or .Net 5.
I'm really wondering that Infragistics does so little information and progress on this tremendous issue. How long do we have to wait for this bug to be fixed?

TIA,
Roman

OMG!!!  You have SO made my day!  There are so many I've missed out on!

Thank you.

Thank you for the explanation Mike, that helps a heap in terms of why something that might seem simple on the surface is taking so long.

Just as a general suggestion, I think that Infragistics would do well to communicate a bit more. I know you've always been reticent about stating release dates and so on, but it would really help to have a better idea of what's going on more regularly.

Also as another suggestion: You guys like to do webinars, but I can absolutely never attend them, do you have those recorded anywhere?  I would love to watch them, but I cannot interrupt my day to day.  I just find webinars whose time I do not control to be inconvenient to the point of just not attending/watching them.  Perhaps there is a place to watch all those recordings and I'm not even aware of it (that'd be a great surprise!). But overall it would be be good to have better communication from Infragistics.

Hi Roman, 

It's not a question of "blame."
Visual Studio itself is a DotNet Framework application. So the Windows Forms designers used to be able to be tightly integrated with the controls themseves. Visual Studio, being a DotNet app, was able to access the controls (which were DotNet controls) directly. 

But now the NetCore controls are no longer based on the DotNet Framework. So Visual Studio can't interact with them directly. So we have to build a whole extra layer of indirection to access the controls in order for the designers to modify them. 

The latest versions of Visual Studio have a framework for this, and we're working on updating our designers to work in NetCore for the next release. 

Hi Mike,

Thanks for your fast answer! If it's not Infragistics who is to blame, I'd like ot apologize. But especially in this case I think Infragistics could state the situation a bit clearer.

My experience since six months is, that the WinForms designer is working well with MS controls, but Infragistics controls seem to fail and we still have to use the workaround, using a full framework project for UI files to make the UI stuff.

Since I don't know what's internally going on and where the problem really is, I hope you can understand that from my point of view, it's an Infragistics issue, even if it isn't.

I'm looking forward to v21.1!

Regards,

Roman