Caught exception is null itself !(捕获的异常本身为空!)
问题描述
我有一个 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);
}
这篇关于捕获的异常本身为空!的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:捕获的异常本身为空!
基础教程推荐
- .NET SerialPort DataReceived 事件未触发 2022-01-01
- C# 从 List<List<int>> 中删除重 2022-01-01
- 禁止输入少量字符,例如'<'、'&a 2022-01-01
- 如果有人提交恶意软件Nuget包怎么办? 2022-01-01
- Moq It.Is<>不匹配 2022-01-01
- WPF 模态进度窗口 2022-01-01
- 如何使用 .Net 检查 Active Directory 服务器是否已启动并正在运行? 2022-01-01
- Azure Functions:CosmosDBTrigger 未在 Visual Studio 中触发 2022-01-01
- 当值可以是对象或空数组时反序列化 JSON 2022-01-01
- 我应该在后面的代码中直接使用 Linq To SQL 还是使 2022-01-01
