Ironically, the only noticeable issue I've encountered so far is an Unhandled exception error when clicking on the "http://www.bizmodeller.com/iHomeServer" link in the "Register iHomeServer" dialog. This exception is consistently triggered when the dialog is invoked from the system tray icon, but I've never seen it when the dialog is invoked from the menu bar in the management console. This doesn't seem to be a fatal error, if I just click the Continue button in the error dialog then the tray icon keeps on running.
I've attached a screenshot of the error and copy of the full text (in UTF-8) from the error dialog Details. Note that there are some characters in the second line of the Exception Text that appear as bullets in the screenshot and unrenderable characters in the text document.
Not to worry, I won't let this minor bug stop me from purchasing a license.
(I checked your bugtracker before posting this report.)
Uploading previously mentioned attachments in formats that are actually allowed by the BBS...
Register iHomeServer error.jpg (75.28 KiB) Viewed 42263 times
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 iHomeServer.Console.RegisterForm.(Object , LinkLabelLinkClickedEventArgs )
at System.Windows.Forms.LinkLabel.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Label.WndProc(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.
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 should add, I was using the latest 64-bit release (version 3.1.84.0) for all of the above testing. However, I just tested your latest posted 64-bit pre-release version 3.1.89.0 and I cannot replicate this bug. So it seems that this issue was addressed somewhere in one of your pre-release versions, though this issue is not mentioned in your Release Notes.
Thanks for letting us know about this bug - am investigating whether it has in fact been resolved as we haven't specifically resolved this between 3.1.84 and 3.1.89, but will double check and if it isn't resolved we'll fix it.
