Hi there
I am having issues viewing my controls in the VIsual Studio 2019 16.10.4 where I am compiling against Infragistcs 2021.1 v 21.1.32-ci
This is in a C# WinForms app targeted at net5.0-windows
Basically none of my controls will display in the designer without errors.
The controls all compile fine and are all usable at runtime, the issue occurs only in the control designer and for even the most basic of controls i.e. a panel that inherits from the UltraPanel and does nothing else
The errors are always the same across all controls.
I have attached the control and a screenshot of the error.
Any ideas would be greatly appreciated.
Regards
Geoff
Hi again
It looks to me like there is an issue with Visual Inheritence in .NET 5 that is NOT there for .NET Framework 4.6.2 when using Infragistcs 2021.1 v 21.1.32-ci
Any control that derives from Infragistics seems to have an issue in .NET 5 whilst there is no issue with .NET 4.6.2
In the attached sample you can see that RamesysPanel has the errors when loading in design view of VS 2019 v16.10.4
where as the UserControl1 control which derives from UserControl has no such issue.
Thanks
WinFormsApp1.zip
Hello Geoff,
I have updated your sample to reference the official release version 21.1.24 instead of 21.1.32-ci.
Can you please test to see if this works in your environment?
Please note that there are still some issues we are currently working on to support Visual Studio version 16.10.
WinForms on Visual Studio 16.10https://www.infragistics.com/community/forums/f/ultimate-ui-for-windows-forms/123150/winforms-on-visual-studio-16-10
WinFormsApp1_mod.zip
Hi Mihoko
Using the attached sample
1/ Open the solution in Visual Studio 2019 v 16.10.4
2/ Compile the application in Debug build
3/ Right click on the RamesysPanel control and choose "View Designer" from the context menu. This control inherits from Infragistics.Win.Misc.UltraPanel
4/ You will get the error when attempting to view the RamesysPanel control in the designer window, I have added a screenshot of the error to the zip file I have attached.
5/ Right click on the UserControl1 control and choose "View Designer" from the context menu. You will NOT get the error with this control. This control inherits from System.Windows.Forms.UserControl
InfragisticsError.zip
I was able to reproduce the issue you are experiencing. I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 273233. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
In response to this issue being logged, I have opened a new private support case for you that I will be linking to this issue so you can be notified when a fix or other resolution becomes available. This private case has an ID of CAS-213625-T7R6Z9 and you can access it here: www.infragistics.com/.../support-activity
Please let me know if you need more information.
Great, thanks for that, please keep me informed.
Hi Geoff, So I have good news and bad news. I tried this out with v 21.1.32-ci and I am seeing the same exception you are getting: the NullReferenceException.Then I tried this same thing with our latest internal build and I do not get that exception any more. So it looks like this will be fixed in the next service release. That's the good news. The bad news is that it looks like Visual Studio doesn't show a designer for Control-derived classes in Net Core. In DotNet Framework, they do. But in Net Core, they only show a designer surface for classes that derive from Form or UserControl. You can see this by creating a class that derives from Control. When I do this, I get an error message that there are no classes to be designed.
Hi Mike
Thanks for the reply.
Yeah that is exactly the conclusion I came to myself thru trial and error.
Interestingly the CustomControl that is available from the Visual Studio "Add New Item" templates derives also from Control and gets a designer error straight out of the box!
I raised this on both Github and Visual Studio Developer Community and both say it is a known issue that is being investigated.
Thanks again