I have a WinForms Window with gridview in it And When this window opens, the following Exception appears
Exception: Exception thrown: 'System.IO.FileNotFoundException' in mscorlib.dll ("Could not load file or assembly 'Telerik.WinControls.XmlSerializers, Version=2017.3.912.40, Culture=neutral' or one of its dependencies. The system cannot find the file specified."). Exception thrown: 'System.IO.FileNotFoundException' in mscorlib.dll ("Could not load file or assembly 'Telerik.WinControls.XmlSerializers, Version=2017.3.912.40, Culture=neutral, PublicKeyToken=a4675be94ecbc7b2' or one of its dependencies. The system cannot find the file specified.")
Whether The App is in the Debug mode or Release mode
How to solve this problem
Thank you very much in advance.
4 Answers, 1 is accepted
You can ignore this exception. Detailed information is available here: Could not load file or assembly Telerik.WinControls.XmlSerializers - Telerik UI for WinForms - KB.
I hope this will be useful. Let me know if you have additional questions.
Regards,
Dimitar
Progress Telerik
`RadImageShape result = new XmlSerializer(typeof(RadImageShape)).Deserialize(xmlTextReader) as RadImageShape;` It's not as though throwing an exception couldn't be avoided here, or at least caught. What a time waster. I keep forgetting that this bug exists, and have had to hunt it down on different occasions.
Hi, Tom,
I am sorry to hear that you are facing any difficulties with the Telerik UI for WinForms suite. Since this forum thread and referred KB article are quite old, I would like to ensure that you encounter exactly the same case or it is a new scenario with the latest version of the Telerik UI for WinForms suite. Could you please elaborate? Could you please specify the exact steps how to reproduce the problem? Thus, we would get better understanding of the precise case and provide further assistance. Thank you in advance.
Tom, Thank you for the sample project. Indeed, if the "Common Language Runtime Exceptions" are enabled, it is possible to experience such a behavior:
However, it doesn't break the application exception and the user can proceed with the execution. This exception is a part of the XmlSerializer's normal operation as it is explained in the referred forum thread.
Although this behavior may seem like an issue, it is the normal behavior of .NET Framework and it is expected. Here is a quote from the MSDN Forums regarding this exception:
"This exception is a part of the XmlSerializer's normal operation. It is expected and will be caught and handled inside of the Framework code. Just ignore it and continue. If it bothers you during debugging, set the Visual Studio debugger to only stop on unhandled exceptions instead of all exceptions."
Additional information is available in the previously referred KB article.
I hope this information helps.
Regards,
Dess
Progress Telerik