我只是遵循了我们通常在java脚本中遵循的方法。将对象转换为字符串，然后检查它们是否为空。

var obj = new Object();
var objStr = obj.ToString();
if (!string.IsNullOrEmpty(objStr)){
  // code as per your needs
}

不，你应该用!=。如果数据实际上是空的，那么你的程序将会因为试图在null上调用Equals方法而导致NullReferenceException崩溃。还要意识到，如果你特别想检查引用是否相等，你应该使用Object。方法，因为你永远不知道Equals是如何实现的。

你的程序崩溃是因为dataList是空的，因为你从来没有初始化它。

c# 6有单值空检查:)

之前:

if (points != null) {
    var next = points.FirstOrDefault();
    if (next != null && next.X != null) return next.X;
}   
return -1;

后:

var bestValue = points?.FirstOrDefault()?.X ?? -1;

使用c#9(2020)，您现在可以使用以下代码检查参数为空:

if (name is null) { }

if (name is not null) { }

你可以在这里获得更多信息

正如其他人已经指出的那样，它不是data，而是dataList是null。除此之外……

catch-throw is an antipattern that almost always makes me want to throw up every time that I see it. Imagine that something goes wrong deep in something that doOtherStuff() calls. All you get back is an Exception object, thrown at the throw in AddData(). No stack trace, no call information, no state, nothing at all to indicate the real source of the problem, unless you go in and switch your debugger to break on exception thrown rather than exception unhandled. If you are catching an exception and just re-throwing it in any way, particularly if the code in the try block is in any way nontrivial, do yourself (and your colleagues, present and future) a favor and throw out the entire try-catch block. Granted, throw; is better than the alternatives, but you are still giving yourself (or whoever else is trying to fix a bug in the code) completely unnecessary headaches. This is not to say that try-catch-throw is necessarily evil per se, as long as you do something relevant with the exception object that was thrown inside the catch block.

然后，首先就存在捕获Exception的潜在问题，但这是另一回事，特别是因为在这种特殊情况下，您抛出了一个异常。

另一件让我感到非常危险的事情是，数据可能在函数执行期间更改值，因为您是通过引用传递的。因此，null检查可能会通过，但在代码对值进行任何操作之前，它已经被更改了——可能是null。我不确定这是否值得关注(可能不是)，但这似乎值得关注。

从c# 9开始你就可以做到

if (obj is null) { ... }

非空用

if (obj is not null) { ... }

如果需要重写此行为，请相应使用==和!=。