Jeffrey L Whitledge是对的。你的' dataList ' -Object本身是空的。

您的代码还有另一个问题:您使用了ref-关键字，这意味着参数数据不能为空!MSDN说:

传递给ref形参的参数必须首先初始化。这与out不同，后者的参数在传递之前不必显式初始化

在“Object”类型中使用泛型也不是一个好主意。泛型应该避免装箱/拆箱，并确保类型安全。如果你想要一个公共类型，让你的方法泛型。最后，你的代码应该是这样的:

public class Foo<T> where T : MyTypeOrInterface {

      public List<T> dataList = new List<T>();

      public bool AddData(ref T data) {
        bool success = false;
        try {
          dataList.Add(data);                   
          success = doOtherStuff(data);
        } catch (Exception e) {
          throw new Exception(e.ToString());
        }
        return success;
      }

      private bool doOtherStuff(T data) {
        //...
      }
    }

正如其他人已经指出的那样，它不是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。我不确定这是否值得关注(可能不是)，但这似乎值得关注。

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

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

你可以像下面这样试试

public List<Object> dataList;
public  bool AddData(ref Object data)
bool success = false;
try
{
    if (data != null)
    {
       dataList.Add(data);
       success = doOtherStuff(data);
    }
}
catch (Exception e)
{
    throw new Exception(e.ToString());
}
return success;

}

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;

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

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