Posted 27 September 2017, 9:13 pm EST
There have been numerous posts dealing with exceptions that occur when debugging an application that uses the C1Editor control with, from what I found, no resolution.
The most common issue surrounds a COMException and typically cannot be recreated by C1 personnel. The reason they could not recreate it is because the appearance of the error is dependent on the Visual Studio (VS) debug settings.
We are getting two different exceptions with the editor control but we only get one at a time and, which one we get depends on the debug settings in VS.
Exception #1: NullReferenceException (this is a first chance exception)
This error occurs in the form designer inside “InitializeComponent()” on this line:
“me.editNote.MaxLength = 7000”.
Exception #2: COMException (this is a “real” exception and not “first chance”)
This error occurs in the form designer inside “InitializeComponent()” on this line:
“Me.editNoteXML = New C1.Win.C1Editor.C1Editor()”
The exception also displays this information:
“An exception of type ‘System.Runtime.InteropServices.COMException’ occurred in
System.Windows.Forms.dll and wasn’t handled before a managed/native boundary”
NOTE: This 2nd error will ONLY occur if the VS debugger has the “Break when exceptions cross AppDomain or managed/native boundaries” option checked. (This option is accessed via:
“DEBUG/Options and Settings” in the “Debugging” section and “General” subsection.)
We would like some resolution on this.
– Paul
