blocks|key|765029|text|是的，它将捕获ApplicationException，因为它是从Exception派生的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|765030|在大多数情况下，处理基本异常应该很好，除非您需要记录或处理不同类型的异常...|765031|try+{
++++if+(isFileDownloaded)
+++++++doSomeThings();
++++else
+++++++throw+new+ApplicationException("Something+expectedly+unexpected+happened.");
}
catch(ApplicationException+e)
{
+++//+log+application+exception+here...
}
catch(Exception+e)
{
+++//+log+all+other+exceptions+here...
}
finally
{
+++//+release+resources...
}|code-block|syntax|javascript|765032|entityMap^0|7|K|X|9|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Yes, it will catch <code>ApplicationException</code> as it derives from <code>Exception</code>.
Handling the base exception should be fine in most cases unless you need to log or do something with a different type of exception...
<pre><code>try {
 if (isFileDownloaded)
 doSomeThings();
 else
 throw new ApplicationException(&quot;Something expectedly unexpected happened.&quot;);
}
catch(ApplicationException e)
{
 // log application exception here...
}
catch(Exception e)
{
 // log all other exceptions here...
}
finally
{
 // release resources...
}
</code></pre>

blocks|key|765054|text|catch将捕获您的异常(以及发生的任何其他异常)。话虽如此，我还是尽量避免写这样的代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|765055|就我个人而言，我看不出有什么理由对同一范围内抛出的异常进行异常处理(catch)。如果你可以在你的方法中处理你的错误--把异常处理(例如:日志记录)直接放在try块中。|765056|在捕捉由try块中的方法抛出的异常时，使用catch更有用。这会更有用，例如，如果您的//+do+stuff节碰巧调用了引发异常的方法。|765057|另外，我建议不要捕获每个异常(Exception+e)，而是捕获您可以正确处理的特定类型的异常。有一个例外是，如果你在catch中重新抛出异常，比如:将它用于日志记录，但仍然让它在调用堆栈中冒泡。|765058|entityMap^0|0|5|0|0|4|3|L|5|17|B|0|F|B|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|M|$]]

The <code>catch</code> will catch your exception (and any other that occurs). That being said, I try to avoid writing code like this when possible.

Personally, I see little reason to ever have exception handling (catch) for an exception thrown in the same scope. If you can handle your error in your method - put the exception handling (ie: logging) directly in the try block as well.

Using a <code>catch</code> is more useful, IMO, for catching exceptions thrown by methods within your <code>try</code> block. This would be more useful, for example, if your <code>// do stuff</code> section happened to call a method that raised an exception.

Also, I recommend not catching every exception (<code>Exception e</code>), but rather the specific types of exceptions you can handle correctly. The one exception to this would be if you're rethrowing the exception within your catch - ie: using it for logging purposes but still letting it bubble up the call stack.

blocks|key|2492844|text|是的，catch会抓住你的ApplicationException，是的，这是糟糕的编码风格。作为一个好的通用规则，只捕获特定的异常和那些你要做的事情，比如修复应用程序状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2492845|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Yes the catch would catch your ApplicationException and yes is is poor coding style. As a good general rule only catch specific exception and those that you are going to do something with, like fixing up application state.

blocks|key|3900549|text|此外，仅供参考，ApplicationException作为派生自的例外从.NET+2.0开始就被弃用了。它从来没有打算自己抛出一个异常，所以你可能根本不应该使用它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3900550|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.applicationexception.aspx^0|8|K|8|K|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Also, FYI, <a href="http://msdn.microsoft.com/en-us/library/system.applicationexception.aspx" rel="nofollow noreferrer"><code>ApplicationException</code></a> has been deprecated since .NET 2.0 as an exception to derive from. It was never intended as an exception to throw on its own, so you probably shouldn't use it at all.

<pre><code>try { 
 if (isFileDownloaded)
 // do stuff
 else
 throw new CustomException()
} 
catch (Exception e)
{
 // something went wrong to save the error to log
}
finally
{
 //release resources
}
</code></pre>
My question is would the <code>catch</code> catches the <code>ApplicationException</code> thrown in the try block? is it in poor coding style?
Should it be written in another way?

Throw an exception in try catch block

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

try {   if (isFileDownloaded)   // do stuff  else   throw new CustomException()} catch (Exception e){  // something went wrong to save the error to log}finally{...

问在try catch块中引发异常
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在try catch块中引发异常EN