当更新遇到500（内部服务器）错误时，VSTO加载项将被禁用 [英] VSTO Add-in Gets Disabled when update encounters 500 (internal server) errors

问题描述

我注意到如果我的托管我的加载项的服务器在处理自动更新时会产生内部服务器错误...抛出异常并且加载项被禁用。

我担心还有其他异常可能导致加载项无法加载。

我已经研究过以编程方式更新加载项，但这似乎过于复杂且不必要。

有没有办法从加载项中捕获这些更新异常或任何其他VSTO运行时异常？或者，是否可以生成Manifest中的设置以继续运行应用程序。例如，当遇到低于500的错误代码时，
更新失败但加载项继续加载。实现此行为的最佳方法是什么？

解决方案

您好Hackmanx1，

我会在这个问题上咨询我的同事。这需要一些时间。非常感谢您的耐心。

很抱歉给您带来不便。

问候，

杰弗里

I noticed that if my server hosting my add-in generates an internal server error when an automatic update is being processed...an exception is thrown and the add-in becomes disabled.

I'm worried that there are other exceptions that could cause the add-in not to load.

I have researched programmatically updating the add-in, but this seems overly complex and unnecessary.

Is there a way to catch these update exceptions or any other VSTO runtime exception from the add-in? Or, is there a setting in the Manifest that can be generated to continue running the application. For example, when error codes below 500 are encountered, the update fails but the add-in continues loading. What is the best way to implement this behavior?

解决方案

Hi Hackmanx1,

I will consult my colleagues on this issue. And it will take some time. Your patience will be greatly appreciated.

Sorry for the inconvenience brought to you.

Regards,

Jeffrey

这篇关于当更新遇到500（内部服务器）错误时，VSTO加载项将被禁用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！