blocks|key|3012667|text|您是如何尝试捕获异常的？通常，从调用Invoke()抛出的是System.Reflection.TargetInvocationException的包装异常实例。您要寻找的实际异常将在InnerException中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3012668|try
{
++++method.Invoke(target,+params);
}
catch+(TargetInvocationException+ex)
{
++++ex+=+ex.InnerException;+//+ex+now+stores+the+original+exception
}|code-block|syntax|javascript|3012669|entityMap^0|I|8|U|17|2K|E|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

How are you trying to catch the exception? Typically what is thrown from a call to <code>Invoke()</code> is a wrapping exception instance of <code>System.Reflection.TargetInvocationException</code>. The actual exception you're after will be in the <code>InnerException</code>.

<pre><code>try
{
 method.Invoke(target, params);
}
catch (TargetInvocationException ex)
{
 ex = ex.InnerException; // ex now stores the original exception
}
</code></pre>

blocks|key|294861|text|编辑:我理解你的问题，这个问题纯粹是一个集成开发环境的问题；你不喜欢VS把调用MethodInfo抛出的异常当作未捕获的异常，而它显然不是。你可以在这里阅读关于如何解决这个问题的文章：Why+is+TargetInvocationException+treated+as+uncaught+by+the+IDE?它看起来像是一个bug+/被设计出来；但无论如何，答案中都列出了一些不错的解决方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|294862|在我看来，您有几个选择：|294863|294864|您可以使用MethodInfo.Invoke，捕获TargetInvocationException并检查其InnerException属性。你必须解决这个答案中提到的集成开发环境的问题。|ordered-list-item|294865|你可以在Delegate之外创建一个合适的MethodInfo并调用它。使用这种技术，抛出的异常将不会被包装。此外，这种方法似乎与调试器配合得很好；我没有得到任何“未捕获的异常”弹出窗口。|294866|294867|下面的示例重点介绍了这两种方法：|294868|class+Program
{
++++static+void+Main()
++++{
++++++++DelegateApproach();
++++++++MethodInfoApproach();
++++}

++++static+void+DelegateApproach()
++++{
++++++++try
++++++++{
++++++++++++Action+action+=+(Action)Delegate.CreateDelegate
+++++++++++++++++++++++++++++++++++(typeof(Action),+GetMethodInfo());
++++++++++++action();
++++++++}
++++++++catch+(NotImplementedException+nie)
++++++++{

++++++++}
+++++}

++++static+void+MethodInfoApproach()
++++{
++++++++try
++++++++{
++++++++++++GetMethodInfo().Invoke(null,+new+object[0]);
++++++++}
++++++++catch+(TargetInvocationException+tie)
++++++++{
++++++++++++if+(tie.InnerException+is+NotImplementedException)
++++++++++++{


++++++++++++}
++++++++}
++++}

++++static+MethodInfo+GetMethodInfo()
++++{
++++++++return+typeof(Program)
++++++++++++++++.GetMethod("TestMethod",+BindingFlags.NonPublic+%7C+BindingFlags.Static);
++++}++++

++++static+void+TestMethod()
++++{
++++++++throw+new+NotImplementedException();
++++}
}|code-block|syntax|javascript|294869|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2658908/why-is-targetinvocationexception-treated-as-uncaught-by-the-ide^0|13|A|2K|1S|0|0|0|0|5|H|P|P|1I|E|0|4|8|L|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|L|3|M|5|K|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1O|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1P|8|@]|D|@]|E|$T|U]]|$1|V|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

EDIT: As I understand your issue, the problem is purely an IDE one; you don't like VS treating the exception thrown by the invocation of the <code>MethodInfo</code> as uncaught, when it clearly isn't. You can read about how to resolve this problem here: <a href="https://stackoverflow.com/questions/2658908/why-is-targetinvocationexception-treated-as-uncaught-by-the-ide">Why is TargetInvocationException treated as uncaught by the IDE?</a> It appears to be a bug / by design; but one way or another, decent workarounds are listed in that answer.

As I see it, you have a couple of options:

<ol>
<li>You can use <code>MethodInfo.Invoke</code>, catch the <code>TargetInvocationException</code> and inspect its <code>InnerException</code> property. You will have to workaround the IDE issues as mentioned in that answer.</li>
<li>You can create an appropriate <code>Delegate</code> out of the <code>MethodInfo</code> and invoke that instead. With this technique, the thrown exception will not be wrapped. Additionally, this approach does seem to play nicely with the debugger; I don't get any "Uncaught exception" pop-ups.</li>
</ol>

Here's an example that highlights both approaches:

<pre><code>class Program
{
 static void Main()
 {
 DelegateApproach();
 MethodInfoApproach();
 }

 static void DelegateApproach()
 {
 try
 {
 Action action = (Action)Delegate.CreateDelegate
 (typeof(Action), GetMethodInfo());
 action();
 }
 catch (NotImplementedException nie)
 {

 }
 }

 static void MethodInfoApproach()
 {
 try
 {
 GetMethodInfo().Invoke(null, new object[0]);
 }
 catch (TargetInvocationException tie)
 {
 if (tie.InnerException is NotImplementedException)
 {


 }
 }
 }

 static MethodInfo GetMethodInfo()
 {
 return typeof(Program)
 .GetMethod("TestMethod", BindingFlags.NonPublic | BindingFlags.Static);
 } 

 static void TestMethod()
 {
 throw new NotImplementedException();
 }
}
</code></pre>

I have a call to <code>MethodInfo.Invoke()</code> to execute a function through reflection. The call is wrapped in a <code>try/catch</code> block but it still won't catch the exception thrown by the function I'm invoking.

I receive the following message:

<blockquote>
 Exception was unhandled by the user.
</blockquote>

 
Why does <code>MethodInfo.Invoke()</code> prevent the Exception to be caught outside of the <code>Invoke()</code>? 
How do I bypass it?

Reflection MethodInfo.Invoke() catch exceptions from inside the method

集成开发环境

调试器

我调用了MethodInfo.Invoke()来通过反射执行函数。调用被包装在一个try/catch块中，但它仍然不能捕获由我正在调用的函数抛出的异常。我收到以下消息：用户未处理异常。为什么MethodInfo.Invoke()要防止异常在Invoke()之外被捕获我如何绕过它？

问反射MethodInfo.Invoke()从方法内部捕获异常
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问反射MethodInfo.Invoke()从方法内部捕获异常EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问反射MethodInfo.Invoke()从方法内部捕获异常
EN