A problem with SyntaxEditor 3.1

SyntaxEditor for Windows Forms Forum

Posted 12 years ago by Kasper
Version: 3.1.0223
Platform: .NET 2.0
Environment: Windows XP (32-bit)
Avatar
Hello,

I have recently updated all my controls from Actipro Software, but now, as I wish to work on an older application, which still uses version 3.1 of SyntaxEditor, it doesn't work anymore. Whenever the SyntaxEditor has focus and I try to press a control key, e.g. Shift, Ctrl or Alt, my application crashes with the following cryptic message:

System.InvalidCastException was unhandled
Message="Unable to cast object of type 'ActiproSoftware.WinUICore.Commands.CommandLink' to type 'ActiproSoftware.WinUICore.Commands.CommandLink'."
Source="ActiproSoftware.WinUICore.Net20"
StackTrace:
at ActiproSoftware.WinUICore.Commands.CommandLinkCollection.get_Item(Int32 index)
at ActiproSoftware.WinUICore.Commands.CommandLinkCollection.GetApplicableCommandLinks(Keys keyCode)
at ActiproSoftware.SyntaxEditor.SyntaxEditor.a(EditorView A_0, Keys A_1, Char A_2, Boolean A_3)
at ActiproSoftware.SyntaxEditor.SyntaxEditor.OnKeyDown(KeyEventArgs 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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at TSW.WebPad.Program.Main(String[] parameters) in C:\TSW\Apps\Source\TSW WebPad.NET\TSW WebPad.NET\Program.cs:line 65
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.Runtime.Hosting.ManifestRunner.Run(Boolean checkAptModel)
at System.Runtime.Hosting.ManifestRunner.ExecuteAsAssembly()
at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext, String[] activationCustomData)
at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssemblyDebugInZone()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()


What's going on here? Was version 3.1 not updated to work with the latest release of the shared library or what? I'm in bit of a hurry, so a fast reply would be really great :)

Comments (1)

Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Kasper,

v3.1 isn't being updated any more except upon request so it probably was looking for an old Shared library. We've rebuilt it and updated the ZIP on the site to use the new Shared/WinUICore libs.


Actipro Software Support

The latest build of this product (v2018.1 build 0341) was released 8 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.