I'm pretty sure everything is still set up correctly. And that it is indeed active in my options.
However, none of the modules are showing up, and the menu to open them is not there, perhaps with the last windows update something happened?
Because you are correct that "Application startup" is occurring, but notice that none of the other modules are loaded like between "2020-04-25 11:33:16,478 and 2020-04-25 11:57:02,62"
Is it possible that an exception is being swallowed somewhere and windows is somehow preventing it from being printed to the log?
Hrm...that's really strange. If you click "go" at the bottom of the second image where it says "Manage: Com add-ins", what does that screen look like? You should see DMsHelper with a checkbox next to it, and behavior should be "load at startup". You can also try checking and unchecking it to see if it forces it to load the add-in.
Also, it's clear from the logs that something is going on. None of the modules are being loaded. I have a striking suspicion that you are throwing an error somewhere and log4net isn't logging it. Maybe there is a call somewhere that needs to surrounded with try/catch? I would imagine this error is happening somewhere in the start of the application.
Also I downloaded 1.1.3 and installed it. Still no menu.
The source hasn't been posted anywhere, no. That said, there's only a very small handful lines of code to loading the plugin specifically to get it in the menu bar. Those lines consist of the loading of the logging framework configuration, and some lines to grab the image files out of the inline resources. The configuration to get it to actually show up in the ribbon bar is actually basically all through an XML file that's installed during the installation of the add-in to office (i don't know where MS Office actually stores these), and not any actual code. It could be tripping up on grabbing out the image files for some reason. I can put together a build later with some extra debugging around that, and see if that yields any results.
The other log entries for loading the modules actually happen when you click a ribbon button, though, so it makes sense that you wouldn't see those if you don't have the buttons to click.
Hey there, here's a quick beta build i put together with extra logging info that it will spit out:
https://www.dropbox.com/s/qal33lhkmrs2vel/v1.2.0-beta.zip?dl=0
This logs before any code is run so that i can see what code it's getting to and what it isn't. Doing some quick testing on my side, it looks like it should hit three total pieces of code during startup:
2020-07-30 08:47:24,541 [1] INFO DMsHelper.Main - Grabbed logging config
2020-07-30 08:47:24,557 [1] INFO DMsHelper.Main - Application startup
2020-07-30 08:47:24,992 [1] INFO DMsHelper.Main - Sending ribbon.xml to oneNote
