Null reference exception ShowDialog after switching to 4.0

Posted 15 years ago by Chris

Version: 10.1.0522

Platform: .NET 4.0

Environment: Windows 7 (32-bit)

We recently switched our project over from 3.5 to 4.0 of the .NET framework and a bunch of wierd stuff started happening. We use the ribbon, property grid, syntax editor, docking and wizard components in our application. The icons on our ribbon started looked like they lost anti-aliasing (very jagged). The wizard is the most obvious so I'll start there. When we call ShowDialog() it now crashes with a NullReferenceException in ActiproSoftware.Wizard.Wpf351 on the ListDictionaryInternal class. Here's the call stack:

at ActiproSoftware.Windows.Controls.Wizard.Automation.Peers.WizardAutomationPeer.GetChildrenCore()
at System.Windows.Automation.Peers.AutomationPeer.EnsureChildren()
at System.Windows.Automation.Peers.AutomationPeer.GetChildren()
at System.Windows.Automation.Peers.AutomationPeer.isDescendantOf(AutomationPeer parent)
at System.Windows.Automation.Peers.AutomationPeer.isDescendantOf(AutomationPeer parent)
at System.Windows.Automation.Peers.AutomationPeer.ValidateConnected(AutomationPeer connectedPeer)
at System.Windows.Automation.Peers.AutomationPeer.AutomationPeerFromInputElement(IInputElement focusedElement)
at System.Windows.Automation.Peers.AutomationPeer.RaiseFocusChangedEventHelper(IInputElement newFocus)
at System.Windows.Input.KeyboardDevice.ChangeFocus(DependencyObject focus, Int32 timestamp)
at System.Windows.Input.KeyboardDevice.TryChangeFocus(DependencyObject newFocus, IKeyboardInputProvider keyboardInputProvider, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
at System.Windows.Input.KeyboardDevice.Focus(DependencyObject focus, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
at System.Windows.Input.KeyboardDevice.Focus(IInputElement element)
at System.Windows.Interop.HwndKeyboardInputProvider.FilterMessage(IntPtr hwnd, WindowMessage message, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.IntGetMessageW(MSG& msg, HandleRef hWnd, Int32 uMsgFilterMin, Int32 uMsgFilterMax)
at MS.Win32.UnsafeNativeMethods.GetMessageW(MSG& msg, HandleRef hWnd, Int32 uMsgFilterMin, Int32 uMsgFilterMax)
at System.Windows.Threading.Dispatcher.GetMessage(MSG& msg, IntPtr hwnd, Int32 minMessage, Int32 maxMessage)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.Show()
at System.Windows.Window.ShowDialog()
at LI.Designer.ViewModels.MainVM.ExecutePublishCommand() in C:\Dev\Workspaces\General\Logical Ink\Designer\ViewModels\MainVM.cs:line 771

The developer upgraded to v10.1.0522 just to make sure it wasn't addressed in a recent fix. Does anyone know what would cause this to occur?

Comments (2)

Posted 15 years ago by Actipro Software Support - Cleveland, OH, USA

Hi Chris,

Thanks for reporting this issue, which we've fixed for the next maintenance release. As a temporary work around you can use the class below instead, until the maintenance release is out. This effectively disables automation for the Wizard, which is where the exception is coming from.

using ActiproSoftware.Windows.Controls.Wizard;

namespace MyNamespace {
    public class MyWizard : Wizard {
        public MyWizard() {
            // Ensure Wizard implicit styles are picked up
            this.SetResourceReference(StyleProperty, typeof(Wizard))
        }
        
        protected override AutomationPeer OnCreateAutomationPeer() {
            // Temporary work around
            return null;
        }
    }
}

Actipro Software Support

Posted 15 years ago by Chris

Thanks - the workaround helped.

The latest build of this product (v24.1.4) was released 1 month ago, which was after the last post in this thread.

Comments (2)

Add Comment