OneNote 2010 加载项加载问题
谷歌搜索 - 可以在这里使用一些帮助。
我在这里遵循了这个出色的教程(http://www.malteahrens.com/#/blog/howto-onenote-dev/)并创建了我自己的 onenote 2010 插件,但我无法将其保留在 onenote 中。第一次安装插件时,我打开 onenote,插件加载得很好(注册表显示加载行为 3)。我关闭 onenote,然后再次打开它,我的插件就被卸载了。 Onenote (options-addins-manage com addins) 显示 com 存在加载错误,并且注册表显示加载行为为 2(错误输出)。具体错误是:
加载行为:未加载。加载 COM 加载项期间发生运行时错误。
我可以启用显示此错误的插件,并且它再次正常工作 - 直到我重新启动应用程序。似乎除了全新安装之外,它无法在任何时候从启动加载。
我已从上述站点的链接之一启用了日志记录,但在日志中没有看到任何有趣的内容。我无法附加到 dllhost.exe 进行调试,因为它没有运行。所以我不知道有什么方法可以看出问题所在。
任何人都知道如何调试此加载错误或它可能是什么的想法?
Googled out- could use some help here.
I followed this excellent tutorial here (http://www.malteahrens.com/#/blog/howto-onenote-dev/) and have created my own onenote 2010 addin, but I am having trouble getting it to STAY in onenote. On first install of the addin, I open onenote and the addin is loaded just fine (registry shows load behavior 3). I close onenote and then simply open it again and my addin is unloaded. Onenote (options-addins-manage com addins) shows there was a load error with com, and the registry shows a load behavior of 2 (errored out). The specific error is:
Load Behavior: Not loaded. A runtime error occurred during the loading of the COM Add-In.
I can enable the plugin displaying this error and it works just fine again- until I restart the app. Seems it just cant load from startup any time except after a fresh install.
Ive enabled logging from one of the links from the site above, and dont see anything interesting in the log. I can't attach to dllhost.exe to debug because its not running. So I don't know any way to even see what is wrong.
Anyone have any ideas how I can debug this load error or ideas of what it might be?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
发现问题 - 我正在签署我的一个程序集,并在不久前重命名了程序集本身。重新生成强程序集签名文件可以解决该问题。
尽管如此,我还是无法找到任何有用的日志信息,因此 sux.txt 可能会有所帮助。
Found the problem- I was signing one of my assemblies and had renamed the assembly itself a bit ago. Regenerating the strong assembly signing file fixes the issue.
Still it was trial and error to find, I was unable to find any useful log info that could have helped, so that sux.