Dear Ladies and Gentlemen

Currently I am trying in vain to upgrade to the latest version Telerik UI for WinForms 2022.1.118.
However, the update fails with the error given below.

I have already uninstalled and reinstalled VS2019. Unfortunately this did not help.

Can you help?

Best Timo

Stop Expanding ALL the Telerik Toolbox control groups when Visual Studio 2017 loads a project! YES, we know your there! We PUT you there.. If we need you, we know where you are! Please quit over-convoluting the toolbox menu by obnoxiously expanding all your toolbox control groups!

To reproduce: please refer to the attached sample video

1. Uninstall the already existing version of the Telerik UI for WinForms suite. Ensure that you don't have any installation and the Telerik menu is not visible in Visual Studio.
2. Open Visual Studio >> Tools >> Extensions and Update and search for Telerik WinForms VSExtensions. Install it.
3. After restarting Visual Studio, create a new Telerik project. You may be prompt to download the latest version during the creation process. 
4. Run the Toolbox configurator in order to obtain the proper version in the toolbox.
5. After the project is created, open the form's designer and drag a Telerik control from the toolbox and drop it onto the form. Open the Designer.cs and you will notice that control's declaration is inside the InitializeComponent method, not outside as expected.

The issue is not reproducible each time you follow the steps. It was reproduced with Visual Stidio 2012 on Windows 10. 

Workaround:

Download the Telerik UI for WinForms msi from your account and install the suite.

I have updated my OS to Win 10 from Win 8.1 and now none of the RadForms will open in VS 2015 Designer. Some esoteric error message: "Value cannot be null. Parameter name: instance" is displayed. Is there something I could do other than re-installing the entire Telerik product line? 

Lajos Szoke

Our development process includes several applications that use the UI for WinForms. As such, we will download the latest release and evaluate all of our applications against it prior to updating all of our developers and our build servers. However, using the Control Panel does not provide any option for maintaining the previous install, so whichever developers are doing the evaluation have to manually reinstall the prior version, or manually install the new version, in order to be able to roll back if we decide not to adopt the latest release. 

Please add an option in the control panel to maintain the previous version when installing updates.

One of the programs we develop is internal, and this makes it a good testing ground for the Telerik updates to make sure there aren't any bugs that will negatively impact customers using the other software we sell. When using the Telerik Control Panel to update to a newer version of Telerik, older versions are forced to be uninstalled. This requires us to go back and reinstall the older versions immediately afterwards until we're ready to update our other software to the latest version of Telerik. It would be very helpful if we could install newer versions without the requirement of uninstalling the older versions.

Thank you!

I've started to use your controls again after a bit of a break. I find myself hunting all over the properties to find the ones I need. How about an option to "pin" a few properties  so that they will be at the top of the list, so they are easy to find?

Upgrade utility miss to change the TelerikData.dll reference. In result, the reference remains pointing to older version of that assembly, which could lead to unexpected exceptions.

Resolution: The issue is no longer reproduced. In Q3 2011 we introduced Upgrade Wizard which replace the Update Utility. 

We just upgraded our WinForm UI from Q3 2013 to Q2 2014 and we started getting a "An unhandled exception of type 'System.TypeinitializationException' occurred in unknown module" before our 'Main' method is ever hit in Program.cs. This didn't occur when we referenced the Q3 2013 assemblies. I've attached the error and our reference list from Solution Explorer in VS 2013 Update 2.