问题描述
我有一个 ASP.NET 应用程序.一切都很好,但最近我得到了一些本身为空的异常:
I have an ASP.NET applications. Everything was fine, but recently I get exceptions that are null themselves:
try { // do something } catch (Exception ex) { Logger.Log("Error while tried to do something. Error: " + ex.Message); }
有时 ex 是 null 本身!
有什么想法吗?
推荐答案
对于到此结束的任何人,我都找到了一个可行的实例(如果只能在调试器中检测到的话).VS2013 更新 4.
For anyone ending up here, I've found an instance where this is possible (If only detectable in the debugger). VS2013 Update 4.
try { // do something } catch (WebException ex) // <- both variables are named 'ex' { Logger.Log("Error while tried to do something. Error: " + ex.Message); } catch (Exception ex) // <- this 'ex' is null { Logger.Log("Error while tried to do something. Error: " + ex.Message); }
解决方案是以不同的方式命名您的异常变量.
The solution is to name your exception variables differently.
try { // do something } catch (WebException webEx) // <- all good in the hood { Logger.Log("Error while tried to do something. Error: " + webEx.Message); // <- } catch (Exception ex) // <- this 'ex' correctly contains the exception { Logger.Log("Error while tried to do something. Error: " + ex.Message); }