|
Glenn Posts: 99
17/04/2020
|
SyMenu has been working great for me for years, from a Dropbox folder shared with others. So I haven't been here for a while. But today, I have a problem, that started a couple weeks ago, maybe after a Windows 10 update, and wasn't fixed by the one I got Tuesday night, so I figured I better report it here (details below, from the error dialog). So when I first encountered it, I would start SyMenu from a Dropbox folder with read-only access, the icon would appear (as usual), and I would click it to get the menu, and this error dialog would appear (which wasn't as usual). If I select continue, the SyMenu icon sticks around, but clicking it produces the dialog again (tried several times). So then Itried Quit button, and the SyMenu icon goes away. So then I start SyMenu again, and can repeat the whole process.
So then, the first time this happened, I then went off to the Dropbox folder with read-write access to SyMenu, which worked fine. Leaving it running, I then went back to the read-only copy, and it worked fine too. I checked with one of my users (who only uses read-only access), and it is working fine for him, but he is using Windows 10 Insider (I think). And other users haven't reported this issue.
Now today, I needed to run this same thing again, and went to the read-only copy, and got the same error dialogs and behavior. I'm about to try the writable copy again. So I start it up, the icon appears, I click it the menu opens, I choose one of the menu items, the command runs successfully, and for variety, and debugging, I close the read-write SyMenu.
Returning to the read-only SyMenu, without the read-write copy running, I get the same error dialogs and behaviors as described above.
Starting the read-write SyMenu, I go into the configuration menu to note the version of SyMenu: v6.01.6493. I've noticed upgrades from time to time, and checking the download page here, I see I'm a few versions back. So maybe this will be fixed by ugrading SyMenu, or maybe not.
With the read-write SyMenu running, I start the read-only SyMenu again. This time it still doesn't work, but behaves as described above.
Trying the update, I get a SyMenu dialog: Error in update process. Please manually download and install SyMenu. It's been so long, I'll have to figure out how again! I wonder if I turned off automatic updates, or why they haven't been happening? Ah yes, found the unchecked Check Version box.
Hmm. Lots of changes since my current version. These look like they might be incompatible...
Fix - A relative working directory (.\) is lo longer resolved from the SyMenu root path but starting from the current item root path
The SyMenu CMD shell is finally removed
Upgrading manually is not covered in the manual, even though the above dialog suggests it. How does one upgrade manually, wihen they already have a configuration they want to use? So the manual does tell where the configuration data is kept; I unpacked the software as directed for a new installation, copy the whole Config folder into the new empty Config folder, and gave it a try, but it was in a different folder than where my commands were, but at least the menus showed up. So then I copied the whole new software+old Config folder back over to the "old installation" area, and it seems to run there, executing at least some of the commands. It would be helpful to mention how to do this in the manual.
So I don't really expect support for old versions of the software, even though I provided as much diagnostic information as I could. I decided to post it all, though, in case someone else experiences something similar.
Microsoft .NET Framework
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Object reference not set to an instance of an object.
Details Continue Quit
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 SyMenu.FormTaskBar.ContextMainMenuShow(ShowMenuEventArgs e)
at SyMenu.FormTaskBar.notifyIcon1_MouseUp(Object sender, MouseEventArgs e)
at System.Windows.Forms.NotifyIcon.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.NotifyIcon.WmMouseUp(Message& m, MouseButtons button)
at System.Windows.Forms.NotifyIcon.WndProc(Message& msg)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SyMenu
Assembly Version: 6.1.6493.31478
Win32 Version: 6.1.6493.31478
CodeBase: file:///D:/my/dropbox/0-gp/SyMenu/SyMenu.exe
----------------------------------------
eFJbeTVfWuEFvWfnBtBecgDqjxNV
Assembly Version: 0.0.0.0
Win32 Version: 6.1.6493.31478
CodeBase: file:///D:/my/dropbox/0-gp/SyMenu/SyMenu.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.XLinq
Assembly Version: 1.0.2319.19042
Win32 Version: 1.0.2319.19042
CodeBase: file:///D:/my/dropbox/0-gp/SyMenu/System.Xml.XLinq.DLL
----------------------------------------
System.Query
Assembly Version: 1.0.2319.19041
Win32 Version: 1.0.2319.19041
CodeBase: file:///D:/my/dropbox/0-gp/SyMenu/System.Query.DLL
----------------------------------------
Ionic.Zip.Reduced
Assembly Version: 1.9.1.8
Win32 Version: 1.9.1.8
CodeBase: file:///D:/my/dropbox/0-gp/SyMenu/Ionic.Zip.Reduced.DLL
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
************** 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:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
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.
|