We’ve installed the latest releases of .Net Micro on several computers without issues except on one laptop where VS2013 and .Net Micro work fine but FEZ Config throws a Microsoft .NET Framework Unhandled exception immediately after I click on FEZ Config in the Programs menu. Here are the details from the error window (also in the attached image).
I’ve uninstalled and reinstalled several times with the same results. I see others have gotten similar errors but don’t see if anyone has resolved this issue. Any Ideas?
[quote]See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I edited the post to try and make it clear. However you got it right, everything works (VS2013, .Net Micro and FEZ Config) on 3 computers. On one computer VS2013 and .Net Micro work but FEZ config throws the exception I described.
If you look at the callstack, it would seem extremely early in app initialization, with Form.OnCreateControl and OnLoad listed. It is probably some left over remnants of a previous FezConfig issue, but how to troubleshoot it without source code is likely a challenge. You could try running procmon and seeing if you can identify what occurs before this.
[quote]System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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) [/quote]
@ Brett - I think it looks like there is a missing configuration file for FEZConfig. I might compare the contents of FEZConfig’s directory on a working machine to the laptop, and copy over any missing files.
I am having the same issue. I can deploy, debug, etc to the Fez Spider, but when I run Fez Config, I get the null reference exception. I have compared Fez Config directory and do not see a difference with a working machine. Maybe a dependency to the application is missing.
After some digging I have found that it is probably a missing or unregistered ocx file that is needed for the main window. Can someone look at the source and verify this for me?
@ elissard - We do not have a dependency on the assembly you mentioned. You can take a look in the Windows event log viewer and see if there is more information about the exception.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at FEZConfig.TinyConfiguaration.TinyConfiguaration_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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)
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.