Intellisense causes exceptions when COM objects are used

SyntaxEditor for Windows Forms Forum

Posted 16 years ago by Ernst
My C# code deals with COM objects. When I type in object name followed by '.' then SyntaxEditor tries to open Intellisense window and it fails. I used the following method to add COM Interop library to the project resolver:


Here is the call stack:

at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.a(IDomType A_0)
at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.GetExtensionMethods(IDomType contextType, String[] importedNamespaces, IDomType targetType, String name, DomBindingFlags flags)
at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetProjectResolver.a(Hashtable A_0, DotNetContext A_1, IDomType A_2, DomBindingFlags A_3)
at ActiproSoftware.SyntaxEditor.Addons.DotNet.Dom.DotNetSyntaxLanguage.b(DotNetLanguage A_0, SyntaxEditor A_1, Boolean A_2)
at ActiproSoftware.SyntaxEditor.Addons.CSharp.CSharpSyntaxLanguage.ShowIntelliPromptMemberList(SyntaxEditor syntaxEditor)
at ActiproSoftware.SyntaxEditor.Addons.CSharp.CSharpSyntaxLanguage.OnSyntaxEditorKeyTyped(SyntaxEditor syntaxEditor, KeyTypedEventArgs e)
at ActiproSoftware.SyntaxEditor.SyntaxEditor.a(EditorView A_0, Keys A_1, Char A_2, Boolean A_3)
at ActiproSoftware.SyntaxEditor.SyntaxEditor.OnKeyPress(KeyPressEventArgs e)
at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
at System.Windows.Forms.Control.WmKeyChar(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at ActiproSoftware.SyntaxEditor.SyntaxEditor.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Comments (1)

Posted 16 years ago by Actipro Software Support - Cleveland, OH, USA
Hi Ernst,

This is really a .NET Languages Add-on question so can you post future related questions in that product's forum? Thanks!

Can you make a simple project that shows this problem happening (include assemblies that are part of the issue) and email it over? We'd need to be able to debug it to figure out what is wrong. Actually you should be able to duplicate it by using the .NET Reflection QuickStart and loading your assembly there. If you can dupe it there, then just email us the assemblies to load and the code to enter.

Actipro Software Support

The latest build of this product (v24.1.0) was released 4 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.