什么是NullReferenceException,我该如何修复?

发布于 2025-01-18 19:05:00 字数 144 浏览 6 评论 0原文

我有一些代码,当它执行时,它会引发nullReferenceException,说:

对象引用未设置为对象的实例。

这是什么意思,我该怎么办来解决此错误?

I have some code and when it executes, it throws a NullReferenceException, saying:

Object reference not set to an instance of an object.

What does this mean, and what can I do to fix this error?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(26

琴流音 2025-01-25 19:05:01

这意味着您的代码使用了一个设置为 null 的对象引用变量(即它没有引用实际的对象实例)。

为了防止该错误,可能为 null 的对象应在使用之前测试是否为 null。

if (myvar != null)
{
    // Go ahead and use myvar
    myvar.property = ...
}
else
{
    // Whoops! myvar is null and cannot be used without first
    // assigning it to an instance reference
    // Attempting to use myvar here will result in NullReferenceException
}

It means your code used an object reference variable that was set to null (i.e. it did not reference an actual object instance).

To prevent the error, objects that could be null should be tested for null before being used.

if (myvar != null)
{
    // Go ahead and use myvar
    myvar.property = ...
}
else
{
    // Whoops! myvar is null and cannot be used without first
    // assigning it to an instance reference
    // Attempting to use myvar here will result in NullReferenceException
}
蝶舞 2025-01-25 19:05:01

这意味着所讨论的变量没有指向任何内容。我可以这样生成:

SqlConnection connection = null;
connection.Open();

这会抛出错误,因为虽然我声明了变量“connection”,但它没有指向任何内容。当我尝试调用成员“Open”时,没有可供解析的引用,并且会抛出错误。

要避免此错误:

  1. 在尝试对对象执行任何操作之前,请务必先初始化它们。
  2. 如果您不确定对象是否为 null,请使用 object == null 进行检查。

JetBrains 的 ReSharper 工具将识别代码中可能存在空引用的每个位置错误,允许您进行空检查。恕我直言,这个错误是错误的第一大来源。

It means that the variable in question is pointed at nothing. I could generate this like so:

SqlConnection connection = null;
connection.Open();

That will throw the error because while I've declared the variable "connection", it's not pointed to anything. When I try to call the member "Open", there's no reference for it to resolve, and it will throw the error.

To avoid this error:

  1. Always initialize your objects before you try to do anything with them.
  2. If you're not sure whether the object is null, check it with object == null.

JetBrains' ReSharper tool will identify every place in your code that has the possibility of a null reference error, allowing you to put in a null check. This error is the number one source of bugs, IMHO.

鼻尖触碰 2025-01-25 19:05:01

请注意,无论何种情况,.NET 中的原因始终相同:

您正在尝试使用值为 Nothing/null 的引用变量。当引用变量的值为 Nothing/null 时,这意味着它实际上并未持有对堆上存在的任何对象实例的引用。

您要么从未为该变量分配过任何内容,也从未创建过分配给该变量的值的实例,要么您手动将变量设置为 Nothing/null,或者您调用了一个函数,为您将变量设置为 Nothing/null

Be aware that regardless of the scenario, the cause is always the same in .NET:

You are trying to use a reference variable whose value is Nothing/null. When the value is Nothing/null for the reference variable, that means it is not actually holding a reference to an instance of any object that exists on the heap.

You either never assigned something to the variable, never created an instance of the value assigned to the variable, or you set the variable equal to Nothing/null manually, or you called a function that set the variable to Nothing/null for you.

风为裳 2025-01-25 19:05:01

抛出此例外的一个例子是:当您试图检查某些东西时,那是无效的。

例如:

string testString = null; //Because it doesn't have a value (i.e. it's null; "Length" cannot do what it needs to do)

if (testString.Length == 0) // Throws a nullreferenceexception
{
    //Do something
} 

当您尝试对未实例化的某些操作(即上述代码)执行操作时,.NET运行时将抛出NullReferenceException。

与一个参数努力相比,如果某种方法期望将其传递给它不是零,则通常将其作为防御措施进行。

更多信息在 c#nullreferenceException和null parameter

An example of this exception being thrown is: When you are trying to check something, that is null.

For example:

string testString = null; //Because it doesn't have a value (i.e. it's null; "Length" cannot do what it needs to do)

if (testString.Length == 0) // Throws a nullreferenceexception
{
    //Do something
} 

The .NET runtime will throw a NullReferenceException when you attempt to perform an action on something which hasn't been instantiated i.e. the code above.

In comparison to an ArgumentNullException which is typically thrown as a defensive measure if a method expects that what is being passed to it is not null.

More information is in C# NullReferenceException and Null Parameter.

无声情话 2025-01-25 19:05:01

更新C#8.0,2019:无效参考类型

C#8.0引入无效的参考类型不可删除的参考类型。因此,仅必须检查可无效的参考类型,以避免 nullReferenceException


如果您尚未初始化参考类型,并且要设置或读取其属性之一,它将抛出 nullReferenceException

示例:

Person p = null;
p.Name = "Harry"; // NullReferenceException occurs here.

您可以通过检查变量是否没有零来避免这种情况:

Person p = null;
if (p!=null)
{
    p.Name = "Harry"; // Not going to run to this point
}

要完全理解为什么要抛出NullReferenceException,重要的是要了解值类型和[参考类型] [3]。

因此,如果您要处理价值类型,则NullReferenceExceptions可能不会发生 。尽管在处理参考类型时,您需要保持警惕!

只有名称建议的参考类型才能将参考文献或点字面上的内容(或“ null”)保存。而价值类型始终包含一个值。

参考类型(必须检查这些类型):

  • 动态
  • 对象
  • 字符串

值类型(您可以简单地忽略这些类型):

  • 数字类型
  • 的积分类型浮点类型
  • 浮点类型
  • DECIMAL
  • BOOL
  • 用户定义结构

Update C#8.0, 2019: Nullable reference types

C#8.0 introduces nullable reference types and non-nullable reference types. So only nullable reference types must be checked to avoid a NullReferenceException.


If you have not initialized a reference type, and you want to set or read one of its properties, it will throw a NullReferenceException.

Example:

Person p = null;
p.Name = "Harry"; // NullReferenceException occurs here.

You can simply avoid this by checking if the variable is not null:

Person p = null;
if (p!=null)
{
    p.Name = "Harry"; // Not going to run to this point
}

To fully understand why a NullReferenceException is thrown, it is important to know the difference between value types and [reference types][3].

So, if you're dealing with value types, NullReferenceExceptions can not occur. Though you need to keep alert when dealing with reference types!

Only reference types, as the name is suggesting, can hold references or point literally to nothing (or 'null'). Whereas value types always contain a value.

Reference types (these ones must be checked):

  • dynamic
  • object
  • string

Value types (you can simply ignore these ones):

  • Numeric types
  • Integral types
  • Floating-point types
  • decimal
  • bool
  • User defined structs
暮年 2025-01-25 19:05:01

可能发生 NullReferenceExceptions 的另一种情况是(不正确)使用 as 运算符

class Book {
    public string Name { get; set; }
}
class Car { }

Car mycar = new Car();
Book mybook = mycar as Book;   // Incompatible conversion --> mybook = null

Console.WriteLine(mybook.Name);   // NullReferenceException

这里,BookCar 是不兼容的类型; 汽车无法转换/转换为书籍。当此转换失败时,as 返回null。此后使用 mybook 会导致 NullReferenceException

一般来说,您应该使用强制转换或as,如下所示:

如果您期望类型转换始终成功(即您提前知道对象应该是什么),那么您应该使用强制转换:

ComicBook cb = (ComicBook)specificBook;

如果您不确定类型,但想要尝试将其用作特定类型,则使用as

ComicBook cb = specificBook as ComicBook;
if (cb != null) {
   // ...
}

Another case where NullReferenceExceptions can happen is the (incorrect) use of the as operator:

class Book {
    public string Name { get; set; }
}
class Car { }

Car mycar = new Car();
Book mybook = mycar as Book;   // Incompatible conversion --> mybook = null

Console.WriteLine(mybook.Name);   // NullReferenceException

Here, Book and Car are incompatible types; a Car cannot be converted/cast to a Book. When this cast fails, as returns null. Using mybook after this causes a NullReferenceException.

In general, you should use a cast or as, as follows:

If you are expecting the type conversion to always succeed (ie. you know what the object should be ahead of time), then you should use a cast:

ComicBook cb = (ComicBook)specificBook;

If you are unsure of the type, but you want to try to use it as a specific type, then use as:

ComicBook cb = specificBook as ComicBook;
if (cb != null) {
   // ...
}
雨巷深深 2025-01-25 19:05:01

您正在使用包含空值引用的对象。所以它给出了一个空异常。在示例中,字符串值为 null,在检查其长度时发生异常。

示例:

string value = null;
if (value.Length == 0) // <-- Causes exception
{
    Console.WriteLine(value); // <-- Never reached
}

异常错误为:

未处理的异常:

System.NullReferenceException:未将对象引用设置到实例
一个物体的。在 Program.Main()

You are using the object that contains the null value reference. So it's giving a null exception. In the example the string value is null and when checking its length, the exception occurred.

Example:

string value = null;
if (value.Length == 0) // <-- Causes exception
{
    Console.WriteLine(value); // <-- Never reached
}

The exception error is:

Unhandled Exception:

System.NullReferenceException: Object reference not set to an instance
of an object. at Program.Main()

梦里的微风 2025-01-25 19:05:01

什么导致NullReferenceExceptions 以及避免/修复此类异常的方法已在其他答案中得到解决,许多程序员尚未学会的是如何独立调试此类异常期间的例外情况 发展。

在 Visual Studio 中,借助 Visual Studio 调试器,这通常很容易。


首先,确保将捕获正确的错误 - 请参阅
如何允许在 VS2010 中中断“System.NullReferenceException”? 注意1< /em>

然后或者 开始调试 (F5 )将[VS 调试器]附加到正在运行的进程。有时使用 Debugger.Break,这将提示启动调试器。

现在,当抛出(或未处理)NullReferenceException 时,调试器将在发生异常的行上停止(还记得上面设置的规则吗?)。有时错误很容易被发现。

例如,
在下面的行中,可能导致异常的唯一代码是如果 myString 计算结果为 null。这可以通过查看观察窗口 或在 立即中运行表达式窗口

var x = myString.Trim();

在更高级的情况下,例如以下情况,您需要使用上述技术之一(Watch 或 Immediate Windows)来检查表达式以确定 str1 是否为 null 或者 str2 为空。

var x = str1.Trim() + str2.Trim();

一旦定位了抛出异常的位置,通常很容易向后推理以找出[错误]引入空值的位置 -

花一些时间来了解异常的原因。检查空表达式。检查可能导致此类空表达式的先前表达式。添加断点 并根据需要逐步执行该程序。 使用调试器。


1 如果 Break on Throws 过于激进并且调试器在 .NET 或第 3 方库中的 NPE 上停止,Break on User-Unhandled 可用于限制捕获的异常。此外,VS2012 引入了Just My Code,我也建议启用它。

如果您在启用“仅我的代码”的情况下进行调试,则行为会略有不同。启用“仅我的代码”后,调试器会忽略在“我的代码”之外引发且不通过“我的代码”的首次公共语言运行时 (CLR) 异常

While what causes a NullReferenceExceptions and approaches to avoid/fix such an exception have been addressed in other answers, what many programmers haven't learned yet is how to independently debug such exceptions during development.

In Visual Studio this is usually easy thanks to the Visual Studio Debugger.


First, make sure that the correct error is going to be caught - see
How do I allow breaking on 'System.NullReferenceException' in VS2010? Note1

Then either Start with Debugging (F5) or Attach [the VS Debugger] to Running Process. On occasion it may be useful to use Debugger.Break, which will prompt to launch the debugger.

Now, when the NullReferenceException is thrown (or unhandled) the debugger will stop (remember the rule set above?) on the line on which the exception occurred. Sometimes the error will be easy to spot.

For instance,
in the following line the only code that can cause the exception is if myString evaluates to null. This can be verified by looking at the Watch Window or running expressions in the Immediate Window.

var x = myString.Trim();

In more advanced cases, such as the following, you'll need to use one of the techniques above (Watch or Immediate Windows) to inspect the expressions to determine if str1 was null or if str2 was null.

var x = str1.Trim() + str2.Trim();

Once where the exception is throw has been located, it's usually trivial to reason backwards to find out where the null value was [incorrectly] introduced --

Take the time required to understand the cause of the exception. Inspect for null expressions. Inspect the previous expressions which could have resulted in such null expressions. Add breakpoints and step through the program as appropriate. Use the debugger.


1 If Break on Throws is too aggressive and the debugger stops on an NPE in the .NET or 3rd-party library, Break on User-Unhandled can be used to limit the exceptions caught. Additionally, VS2012 introduces Just My Code which I recommend enabling as well.

If you are debugging with Just My Code enabled, the behavior is slightly different. With Just My Code enabled, the debugger ignores first-chance common language runtime (CLR) exceptions that are thrown outside of My Code and do not pass through My Code

妄断弥空 2025-01-25 19:05:01

Simon Mourier给了这个示例

object o = null;
DateTime d = (DateTime)o;  // NullReferenceException

其中 unboxing 转换(铸造(铸造) )来自 object(或从类别之一system.valuetypesystem.enum,或从接口type) to 一个值类型(nullable&lt;&gt;)本身给出了nullReferenceException

在另一个方向上,来自 a a nullable&lt;&gt;&gt; 拳击 转换代码>等于false to 参考类型,可以给出null参考,然后可以稍后引入NullReferenceException。经典的例子是:

DateTime? d = null;
var s = d.ToString();  // OK, no exception (no boxing), returns ""
var t = d.GetType();   // Bang! d is boxed, NullReferenceException

有时拳击会以另一种方式发生。例如,使用此非传播扩展方法:

public static void MyExtension(this object x)
{
  x.ToString();
}

以下代码将是有问题的:

DateTime? d = null;
d.MyExtension();  // Leads to boxing, NullReferenceException occurs inside the body of the called method, not here.

这些情况是由于运行时在拳击nullable时使用的特殊规则而出现的。

Simon Mourier gave this example:

object o = null;
DateTime d = (DateTime)o;  // NullReferenceException

where an unboxing conversion (cast) from object (or from one of the classes System.ValueType or System.Enum, or from an interface type) to a value type (other than Nullable<>) in itself gives the NullReferenceException.

In the other direction, a boxing conversion from a Nullable<> which has HasValue equal to false to a reference type, can give a null reference which can then later lead to a NullReferenceException. The classic example is:

DateTime? d = null;
var s = d.ToString();  // OK, no exception (no boxing), returns ""
var t = d.GetType();   // Bang! d is boxed, NullReferenceException

Sometimes the boxing happens in another way. For example with this non-generic extension method:

public static void MyExtension(this object x)
{
  x.ToString();
}

the following code will be problematic:

DateTime? d = null;
d.MyExtension();  // Leads to boxing, NullReferenceException occurs inside the body of the called method, not here.

These cases arise because of the special rules the runtime uses when boxing Nullable<> instances.

╰つ倒转 2025-01-25 19:05:01

当实体框架中使用的实体的类名称与Web表单代码范围文件的类名称相同时,添加一个案例。

假设您有一个Web表单Contact.ASPX,其CodeBehind类是联系人,并且您具有实体名称联系人。

请在调用Context.SaveChanges()时,以下代码将丢弃NullReferenceException

Contact contact = new Contact { Name = "Abhinav"};
var context = new DataContext();
context.Contacts.Add(contact);
context.SaveChanges(); // NullReferenceException at this line

然后,为了完整的dataContext类

public class DataContext : DbContext 
{
    public DbSet<Contact> Contacts {get; set;}
}

和联系人实体类, 。有时,实体类是部分类,因此您也可以在其他文件中扩展它们。

public partial class Contact 
{
    public string Name {get; set;}
}

当实体和CodeBehind类处于同一名称空间时,发生错误。
要解决此问题,请重命名实体类或CodeBehind类以供contact.aspx。

原因
我仍然不确定原因。但是,每当任何实体类都扩展system.web.ui.page时,此错误就会发生。

为了讨论,请查看 nullReReference exception in dbcontext.savechanges()

Adding a case when the class name for entity used in entity framework is same as class name for a web form code-behind file.

Suppose you have a web form Contact.aspx whose codebehind class is Contact and you have an entity name Contact.

Then following code will throw a NullReferenceException when you call context.SaveChanges()

Contact contact = new Contact { Name = "Abhinav"};
var context = new DataContext();
context.Contacts.Add(contact);
context.SaveChanges(); // NullReferenceException at this line

For the sake of completeness DataContext class

public class DataContext : DbContext 
{
    public DbSet<Contact> Contacts {get; set;}
}

and Contact entity class. Sometimes entity classes are partial classes so that you can extend them in other files too.

public partial class Contact 
{
    public string Name {get; set;}
}

The error occurs when both the entity and codebehind class are in same namespace.
To fix this, rename the entity class or the codebehind class for Contact.aspx.

Reason
I am still not sure about the reason. But whenever any of the entity class will extend System.Web.UI.Page this error occurs.

For discussion have a look at NullReferenceException in DbContext.saveChanges()

混浊又暗下来 2025-01-25 19:05:01

另一种可能收到此异常的常见情况涉及在单元测试期间模拟类。无论使用哪种模拟框架,您都必须确保正确模拟类层次结构的所有适当级别。特别是,被测试代码引用的 HttpContext 的所有属性都必须被模拟。

请参阅“测试自定义 AuthorizationAttribute 时抛出 NullReferenceException”以获得稍微详细的示例。

Another general case where one might receive this exception involves mocking classes during unit testing. Regardless of the mocking framework being used, you must ensure that all appropriate levels of the class hierarchy are properly mocked. In particular, all properties of HttpContext which are referenced by the code under test must be mocked.

See "NullReferenceException thrown when testing custom AuthorizationAttribute" for a somewhat verbose example.

神魇的王 2025-01-25 19:05:01

我对这个问题有不同的看法。这种答案“我还能做什么来避免它?

跨不同层工作时,例如在 MVC 应用程序中,控制器需要服务来调用业务操作。在这种情况下,可以使用依赖注入容器来初始化服务以避免NullReferenceException。因此,这意味着您无需担心检查 null,只需从控制器调用服务,就好像它们始终作为单例或原型可用(并初始化)一样。

public class MyController
{
    private ServiceA serviceA;
    private ServiceB serviceB;

    public MyController(ServiceA serviceA, ServiceB serviceB)
    {
        this.serviceA = serviceA;
        this.serviceB = serviceB;
    }

    public void MyMethod()
    {
        // We don't need to check null because the dependency injection container 
        // injects it, provided you took care of bootstrapping it.
        var someObject = serviceA.DoThis();
    }
}

I have a different perspective to answering this. This sort of answers "what else can I do to avoid it?"

When working across different layers, for example in an MVC application, a controller needs services to call business operations. In such scenarios Dependency Injection Container can be used to initialize the services to avoid the NullReferenceException. So that means you don't need to worry about checking for null and just call the services from the controller as though they will always to available (and initialized) as either a singleton or a prototype.

public class MyController
{
    private ServiceA serviceA;
    private ServiceB serviceB;

    public MyController(ServiceA serviceA, ServiceB serviceB)
    {
        this.serviceA = serviceA;
        this.serviceB = serviceB;
    }

    public void MyMethod()
    {
        // We don't need to check null because the dependency injection container 
        // injects it, provided you took care of bootstrapping it.
        var someObject = serviceA.DoThis();
    }
}
各空 2025-01-25 19:05:01

关于“我该怎么办”这个问题,可以有很多答案。

在开发时防止此类错误情况的一种更“正式”的方法是应用在代码中按契约设计。这意味着您需要在开发时在系统上设置类不变量,和/或什至函数/方法前置条件后置条件

简而言之,类不变量确保您的类中存在一些在正常使用中不会被违反的约束(因此,该类不会处于不一致的状态)。 先决条件意味着作为函数/方法的输入给出的数据必须遵循一些约束集并且决不违反它们,而后置条件意味着函数/方法输出必须再次遵循设定的约束,而不能违反它们。
在执行无错误程序期间绝不违反合同条件,因此在调试模式下实际上会检查合同设计,同时在发布中禁用,以最大限度地提高开发的系统性能。

这样,您可以避免因违反约束集而导致的 NullReferenceException 情况。例如,如果您在类中使用对象属性 X,然后尝试调用其方法之一,而 X 具有 null 值,则这将导致 NullReferenceException

public X { get; set; }

public void InvokeX()
{
    X.DoSomething(); // if X value is null, you will get a NullReferenceException
}

但是,如果您将“属性 X 绝不能有空值”设置为方法前提条件,那么您可以防止前面描述的情况:

//Using code contracts:
[ContractInvariantMethod]
protected void ObjectInvariant() 
{
    Contract.Invariant(X != null);
    //...
}

因此,代码合同项目存在对于.NET应用程序。

或者,可以使用断言来应用按合同设计

更新:值得一提的是,该术语是由 Bertrand Meyer 创造的 与他设计的 Eiffel 编程语言有关

On the matter of "what should I do about it", there can be many answers.

A more "formal" way of preventing such error conditions while developing is applying design by contract in your code. This means you need to set class invariants, and/or even function/method preconditions and postconditions on your system, while developing.

In short, class invariants ensure that there will be some constraints in your class that will not get violated in normal use (and therefore, the class will not get in an inconsistent state). Preconditions mean that data given as input to a function/method must follow some constraints set and never violate them, and postconditions mean that a function/method output must follow the set constraints again without ever violating them.
Contract conditions should never be violated during execution of a bug-free program, therefore design by contract is checked in practice in debug mode, while being disabled in releases, to maximize the developed system performance.

This way, you can avoid NullReferenceException cases that are results of violation of the constraints set. For example, if you use an object property X in a class and later try to invoke one of its methods and X has a null value, then this will lead to NullReferenceException:

public X { get; set; }

public void InvokeX()
{
    X.DoSomething(); // if X value is null, you will get a NullReferenceException
}

But if you set "property X must never have a null value" as method precondition, then you can prevent the scenario described before:

//Using code contracts:
[ContractInvariantMethod]
protected void ObjectInvariant() 
{
    Contract.Invariant(X != null);
    //...
}

For this cause, Code Contracts project exists for .NET applications.

Alternatively, design by contract can be applied using assertions.

UPDATE: It is worth mentioning that the term was coined by Bertrand Meyer in connection with his design of the Eiffel programming language.

时光清浅 2025-01-25 19:05:01

当我们尝试访问空对象的属性时,或者当字符串值变为空并且我们尝试访问字符串方法时,会抛出 NullReferenceException 。

例如:

  1. 当访问空字符串的字符串方法时:

    字符串 str = string.Empty;
    str.ToLower(); // 抛出空引用异常
    
  2. 当访问空对象的属性时:

    公共类人 {
        公共字符串名称{获取;放; }
    }
    人 objPerson;
    objPerson.Name /// 抛出空引用异常 
    

A NullReferenceException is thrown when we are trying to access Properties of a null object or when a string value becomes empty and we are trying to access string methods.

For example:

  1. When a string method of an empty string accessed:

    string str = string.Empty;
    str.ToLower(); // throw null reference exception
    
  2. When a property of a null object accessed:

    Public Class Person {
        public string Name { get; set; }
    }
    Person objPerson;
    objPerson.Name  /// throw Null refernce Exception 
    
全部不再 2025-01-25 19:05:01

TL;DR:尝试使用Html.Partial而不是Renderpage


我得到对象引用未设置到对象的实例< /code> 当我尝试通过向视图发送模型来渲染视图中的视图时,如下所示:

@{
    MyEntity M = new MyEntity();
}
@RenderPage("_MyOtherView.cshtml", M); // error in _MyOtherView, the Model was Null

调试显示模型在 MyOtherView 中为 Null。直到我将其更改为:

@{
    MyEntity M = new MyEntity();
}
@Html.Partial("_MyOtherView.cshtml", M);

并且它起作用了。

此外,我一开始就没有 Html.Partial 的原因是 Visual Studio 有时Html.Partial 下抛出看起来错误的波浪线> 如果它位于不同构造的 foreach 循环内,即使它并不是真正的错误:

@inherits System.Web.Mvc.WebViewPage
@{
    ViewBag.Title = "Entity Index";
    List<MyEntity> MyEntities = new List<MyEntity>();
    MyEntities.Add(new MyEntity());
    MyEntities.Add(new MyEntity());
    MyEntities.Add(new MyEntity());
}
<div>
    @{
        foreach(var M in MyEntities)
        {
            // Squiggly lines below. Hovering says: cannot convert method group 'partial' to non-delegate type Object, did you intend to envoke the Method?
            @Html.Partial("MyOtherView.cshtml");
        }
    }
</div>

但我能够运行该应用程序,而不会出现此“错误”的问题。我能够通过将 foreach 循环的结构更改为如下所示来消除该错误:

@foreach(var M in MyEntities){
    ...
}

虽然我有一种感觉,这是因为 Visual Studio 误读了 & 符号和括号。

TL;DR: Try using Html.Partial instead of Renderpage


I was getting Object reference not set to an instance of an object when I tried to render a View within a View by sending it a Model, like this:

@{
    MyEntity M = new MyEntity();
}
@RenderPage("_MyOtherView.cshtml", M); // error in _MyOtherView, the Model was Null

Debugging showed the model was Null inside MyOtherView. Until I changed it to:

@{
    MyEntity M = new MyEntity();
}
@Html.Partial("_MyOtherView.cshtml", M);

And it worked.

Furthermore, the reason I didn't have Html.Partial to begin with was because Visual Studio sometimes throws error-looking squiggly lines under Html.Partial if it's inside a differently constructed foreach loop, even though it's not really an error:

@inherits System.Web.Mvc.WebViewPage
@{
    ViewBag.Title = "Entity Index";
    List<MyEntity> MyEntities = new List<MyEntity>();
    MyEntities.Add(new MyEntity());
    MyEntities.Add(new MyEntity());
    MyEntities.Add(new MyEntity());
}
<div>
    @{
        foreach(var M in MyEntities)
        {
            // Squiggly lines below. Hovering says: cannot convert method group 'partial' to non-delegate type Object, did you intend to envoke the Method?
            @Html.Partial("MyOtherView.cshtml");
        }
    }
</div>

But I was able to run the application with no problems with this "error". I was able to get rid of the error by changing the structure of the foreach loop to look like this:

@foreach(var M in MyEntities){
    ...
}

Although I have a feeling it was because Visual Studio was misreading the ampersands and brackets.

醉生梦死 2025-01-25 19:05:01

您该怎么办?

这里有很多好的答案,解释了什么是无效的引用以及如何调试它。但是,如何防止问题或至少使捕获更容易。

检查参数

例如,方法可以检查不同的参数,以查看它们是否为null并投掷gongementnullexception,显然是出于此确切目的而创建的例外。

参数Nullexception的构造函数甚至以参数的名称和消息作为参数,因此您可以确切地告诉开发人员问题是什么。

public void DoSomething(MyObject obj) {
    if(obj == null) 
    {
        throw new ArgumentNullException("obj", "Need a reference to obj.");
    }
}

使用工具

也有几个库可以提供帮助。例如,“ Resharper”可以在编写代码时为您提供警告,尤其是如果您使用其属性: notnullattribute

有“ Microsoft Code Contracts”,您使用语法,例如Contract.requires.requires(obj!= null),可以为您提供运行时和编译时间:介绍代码合同

还有“ PostSharp”,它将允许您仅使用类似的属性:

public void DoSometing([NotNull] obj)

通过这样做并将后期换成构建过程的一部分obj将在运行时检查NULL的null。请参阅: noreferrer“

普通代码解决方案

,也可以使用普通的旧代码来编码自己的方法。例如,这里是一个结构,您可以使用该结构来获取零引用。它以与Nullable&lt; t&gt;相同的概念进行建模:

[System.Diagnostics.DebuggerNonUserCode]
public struct NotNull<T> where T: class
{
    private T _value;

    public T Value
    {
        get
        {
            if (_value == null)
            {
                throw new Exception("null value not allowed");
            }

            return _value;
        }
        set
        {
            if (value == null)
            {
                throw new Exception("null value not allowed.");
            }

            _value = value;
        }
    }

    public static implicit operator T(NotNull<T> notNullValue)
    {
        return notNullValue.Value;
    }

    public static implicit operator NotNull<T>(T value)
    {
        return new NotNull<T> { Value = value };
    }
}

您将使用与使用nullable&lt; t&gt;相同的方式使用的方式,但目的是确切地完成。相反 - 不允许null。以下是一些示例:

NotNull<Person> person = null; // throws exception
NotNull<Person> person = new Person(); // OK
NotNull<Person> person = GetPerson(); // throws exception if GetPerson() returns null

notnull&lt; t&gt;被隐式地投入到t中,因此您几乎可以在任何需要的地方使用它。例如,您可以将person对象传递到采用notnull&lt; person&gt;的方法:

Person person = new Person { Name = "John" };
WriteName(person);

public static void WriteName(NotNull<Person> person)
{
    Console.WriteLine(person.Value.Name);
}

如上所述,您可以通过无效的方式访问基础值value属性。另外,您可以使用明确或隐式铸件,您可以在下面看到一个示例:

Person person = GetPerson();

public static NotNull<Person> GetPerson()
{
    return new Person { Name = "John" };
}

或者,当方法刚刚返回t(在这种情况下,您甚至可以使用它) /code>)通过演员表。例如,以下代码与上述代码相似:

Person person = (NotNull<Person>)GetPerson();

public static Person GetPerson()
{
    return new Person { Name = "John" };
}

与扩展名相结合

combine notnull&lt; t&gt;使用扩展方法,您可以涵盖更多情况。以下是扩展方法的外观示例:

[System.Diagnostics.DebuggerNonUserCode]
public static class NotNullExtension
{
    public static T NotNull<T>(this T @this) where T: class
    {
        if (@this == null)
        {
            throw new Exception("null value not allowed");
        }

        return @this;
    }
}

这是一个可以使用的示例:

var person = GetPerson().NotNull();

github

用于您的参考,我在GitHub上提供了上面的代码,您可以在:

https://github.com/luisperezphd/notnull

相关语言功能

c#6.0操作员“对此有所帮助。使用此功能,您可以引用嵌套对象,如果其中任何一个是null整个表达式返回null

这减少了您在某些情况下必须进行的空检查数量。语法是要在每个点之前放一个问号。以以下代码为例:

var address = country?.State?.County?.City;

想象一下country是类型country具有称为state的属性的对象。如果country状态,或code> city is null然后地址将为 null 。因此,您只需要检查地址是否 null`。

这是一个很棒的功能,但它为您提供了更少的信息。这并不明显4个为null。

内置像无效的?

c#有一个不错的速记,适用于nullable&lt; t&gt;,您可以通过在类型之后放置一个so int so int的问号来使某些内容无效?

如果c#有notnull&lt; t&gt; struct上面并且具有类似的速记,也许是感叹号(!),这样您就可以写出类似的内容,这样您就可以写下类似的内容:public> public void writename,那将是很好的。 (人!人)

What can you do about it?

There is a lot of good answers here explaining what a null reference is and how to debug it. But there is very little on how to prevent the issue or at least make it easier to catch.

Check arguments

For example, methods can check the different arguments to see if they are null and throw an ArgumentNullException, an exception obviously created for this exact purpose.

The constructor for the ArgumentNullException even takes the name of the parameter and a message as arguments so you can tell the developer exactly what the problem is.

public void DoSomething(MyObject obj) {
    if(obj == null) 
    {
        throw new ArgumentNullException("obj", "Need a reference to obj.");
    }
}

Use Tools

There are also several libraries that can help. "Resharper" for example can provide you with warnings while you are writing code, especially if you use their attribute: NotNullAttribute

There's "Microsoft Code Contracts" where you use syntax like Contract.Requires(obj != null) which gives you runtime and compile checking: Introducing Code Contracts.

There's also "PostSharp" which will allow you to just use attributes like this:

public void DoSometing([NotNull] obj)

By doing that and making PostSharp part of your build process obj will be checked for null at runtime. See: PostSharp null check

Plain Code Solution

Or you can always code your own approach using plain old code. For example here is a struct that you can use to catch null references. It's modeled after the same concept as Nullable<T>:

[System.Diagnostics.DebuggerNonUserCode]
public struct NotNull<T> where T: class
{
    private T _value;

    public T Value
    {
        get
        {
            if (_value == null)
            {
                throw new Exception("null value not allowed");
            }

            return _value;
        }
        set
        {
            if (value == null)
            {
                throw new Exception("null value not allowed.");
            }

            _value = value;
        }
    }

    public static implicit operator T(NotNull<T> notNullValue)
    {
        return notNullValue.Value;
    }

    public static implicit operator NotNull<T>(T value)
    {
        return new NotNull<T> { Value = value };
    }
}

You would use very similar to the same way you would use Nullable<T>, except with the goal of accomplishing exactly the opposite - to not allow null. Here are some examples:

NotNull<Person> person = null; // throws exception
NotNull<Person> person = new Person(); // OK
NotNull<Person> person = GetPerson(); // throws exception if GetPerson() returns null

NotNull<T> is implicitly cast to and from T so you can use it just about anywhere you need it. For example, you can pass a Person object to a method that takes a NotNull<Person>:

Person person = new Person { Name = "John" };
WriteName(person);

public static void WriteName(NotNull<Person> person)
{
    Console.WriteLine(person.Value.Name);
}

As you can see above as with nullable you would access the underlying value through the Value property. Alternatively, you can use an explicit or implicit cast, you can see an example with the return value below:

Person person = GetPerson();

public static NotNull<Person> GetPerson()
{
    return new Person { Name = "John" };
}

Or you can even use it when the method just returns T (in this case Person) by doing a cast. For example, the following code would just like the code above:

Person person = (NotNull<Person>)GetPerson();

public static Person GetPerson()
{
    return new Person { Name = "John" };
}

Combine with Extension

Combine NotNull<T> with an extension method and you can cover even more situations. Here is an example of what the extension method can look like:

[System.Diagnostics.DebuggerNonUserCode]
public static class NotNullExtension
{
    public static T NotNull<T>(this T @this) where T: class
    {
        if (@this == null)
        {
            throw new Exception("null value not allowed");
        }

        return @this;
    }
}

And here is an example of how it could be used:

var person = GetPerson().NotNull();

GitHub

For your reference I made the code above available on GitHub, you can find it at:

https://github.com/luisperezphd/NotNull

Related Language Feature

C# 6.0 introduced the "null-conditional operator" that helps with this a little. With this feature, you can reference nested objects and if any one of them is null the whole expression returns null.

This reduces the number of null checks you have to do in some cases. The syntax is to put a question mark before each dot. Take the following code for example:

var address = country?.State?.County?.City;

Imagine that country is an object of type Country that has a property called State and so on. If country, State, County, or City is null then address will benull. Therefore you only have to check whetheraddressisnull`.

It's a great feature, but it gives you less information. It doesn't make it obvious which of the 4 is null.

Built-in like Nullable?

C# has a nice shorthand for Nullable<T>, you can make something nullable by putting a question mark after the type like so int?.

It would be nice if C# had something like the NotNull<T> struct above and had a similar shorthand, maybe the exclamation point (!) so that you could write something like: public void WriteName(Person! person).

疧_╮線 2025-01-25 19:05:01

您可以使用c#6中的无条件运算符以干净的方式修复NullReferenceException,并编写较少的代码来处理无效检查。

它用于在执行成员访问(?)或索引(?[)操作之前测试NULL。

示例

  var name = p?.Spouse?.FirstName;

等于:

    if (p != null)
    {
        if (p.Spouse != null)
        {
            name = p.Spouse.FirstName;
        }
    }

结果是,当p为null或p.p.spouse为null时,名称将为null。

否则,将分配变量名称p.spouse.firstname的值。

对于更多详细信息: null条件运算符

You can fix NullReferenceException in a clean way using Null-conditional Operators in C# 6 and write less code to handle null checks.

It's used to test for null before performing a member access (?.) or index (?[) operation.

Example

  var name = p?.Spouse?.FirstName;

It is equivalent to:

    if (p != null)
    {
        if (p.Spouse != null)
        {
            name = p.Spouse.FirstName;
        }
    }

The result is that the name will be null when p is null or when p.Spouse is null.

Otherwise, the variable name will be assigned the value of the p.Spouse.FirstName.

For more details: Null-conditional Operators

Bonjour°[大白 2025-01-25 19:05:01

有趣的是,本页上的所有答案都没有提到这两种边缘情况:

边缘情况 #1:并发访问字典

.NET 中的通用字典不是线程安全的,它们有时可能会抛出NullReference 甚至(更常见)出现 KeyNotFoundException。在这种情况下,异常是相当具有误导性的。

边缘情况 #2:不安全代码

如果 unsafe 代码引发 NullReferenceException,您可能会查看指针变量,并检查它们是否有 IntPtr.Zero代码>或其他东西。这是同样的事情(“空指针异常”),但是在不安全的代码中,变量通常会被转换为值类型/数组等,并且你会用头撞墙,想知道值类型如何抛出这个异常例外。

(顺便说一句,除非您需要,否则不使用不安全代码的另一个原因。)

边缘情况 #3:Visual Studio 多显示器设置与辅助显示器的 DPI 设置与主显示器不同

这种边缘情况是软件 -具体并属于 Visual Studio 2019 IDE(可能还有早期版本)。

重现该问题的方法:将工具箱中的任何组件拖动到具有与主显示器不同的 DPI 设置的非主显示器上的 Windows 窗体,然后您会收到一个弹出窗口,其中显示“对象引用未设置为目的。”根据 这个线程,这个问题已经存在很长一段时间了,在撰写本文时它仍然没有得到解决。

Interestingly, none of the answers on this page mention the two edge cases:

Edge case #1: concurrent access to a Dictionary

Generic dictionaries in .NET are not thread-safe and they sometimes might throw a NullReference or even (more frequent) a KeyNotFoundException when you try to access a key from two concurrent threads. The exception is quite misleading in this case.

Edge case #2: unsafe code

If a NullReferenceException is thrown by unsafe code, you might look at your pointer variables, and check them for IntPtr.Zero or something. Which is the same thing ("null pointer exception"), but in unsafe code, variables are often cast to value-types/arrays, etc., and you bang your head against the wall, wondering how a value-type can throw this exception.

(Another reason for non-using unsafe code unless you need it, by the way.)

Edge case #3: Visual Studio multi monitor setup with secondary monitor(s) that has different DPI setting than the primary monitor

This edge case is software-specific and pertains to the Visual Studio 2019 IDE (and possibly earlier versions).

A method to reproduce the problem: drag any component from the Toolbox to a Windows form on a non-primary monitor with different DPI setting than the primary monitor, and you get a pop-up with “Object reference not set to an instance of an object.” According to this thread, this issue has been known for quite some time and at the time of writing it still hasn't been fixed.

素罗衫 2025-01-25 19:05:01

错误行“未设置为对象的实例”。指出您尚未将实例对象分配给对象引用,并且您仍在访问该对象的属性/方法。

例如:假设您有一个名为MyClass的课程,它包含一个属性, prop1

public Class myClass
{
   public int prop1 {get;set;}
}

现在,您正在其他某些类中访问此Prop1,就像以下类似:

public class Demo
{
     public void testMethod()
     {
        myClass ref = null;
        ref.prop1 = 1;  // This line throws an error
     }
}

上面的行引发了错误,因为声明了类myClass的引用,但未实例化或对象实例未分配给该类的参考。

要解决此问题,您必须实例化(将对象分配给该类的引用)。

public class Demo
{
     public void testMethod()
     {
        myClass ref = null;
        ref = new myClass();
        ref.prop1 = 1;
     }
}

The error line "Object reference not set to an instance of an object." states that you have not assigned an instance object to a object reference and still you are accessing properties/methods of that object.

For example: let's say you have a class called myClass and it contains one property, prop1.

public Class myClass
{
   public int prop1 {get;set;}
}

Now you are accessing this prop1 in some other class just like below:

public class Demo
{
     public void testMethod()
     {
        myClass ref = null;
        ref.prop1 = 1;  // This line throws an error
     }
}

The above line throws an error because reference of class myClass is declared, but not instantiated or an instance of object is not assigned to a reference of that class.

To fix this you have to instantiate (assign an object to a reference of that class).

public class Demo
{
     public void testMethod()
     {
        myClass ref = null;
        ref = new myClass();
        ref.prop1 = 1;
     }
}
余罪 2025-01-25 19:05:01

简单来说:

您正在尝试访问未创建或当前不在内存中的对象。

那么如何解决这个问题:

  1. 调试并让调试器中断...它会直接将您带到损坏的变量...现在您的任务是简单地修复这个问题..使用new

  2. 如果它是由某些数据库命令引起的,因为对象不存在,那么您需要做的就是进行空检查并处理它:

    if (i == null) {
        // 处理这个
    }
    
  3. 最难的一个..如果GC已经收集了对象...这通常发生在以下情况:你正试图使用​​字符串来查找一个对象...也就是说,通过对象的名称来查找它,那么GC可能已经清理了它...这很难找到,并且会成为一个很大的问题..解决这个问题的更好方法是在开发过程中根据需要进行空检查。这将为您节省大量时间。

按名称查找是指某些框架允许您使用字符串查找对象,代码可能如下所示: FindObject("ObjectName");

Well, in simple terms:

You are trying to access an object that isn't created or currently not in memory.

So how to tackle this:

  1. Debug and let the debugger break... It will directly take you to the variable that is broken... Now your task is to simply fix this.. Using the new keyword in the appropriate place.

  2. If it is caused on some database commands because the object isn't present then all you need to do is do a null check and handle it:

    if (i == null) {
        // Handle this
    }
    
  3. The hardest one .. if the GC collected the object already... This generally occurs if you are trying to find an object using strings... That is, finding it by name of the object then it may happen that the GC might already cleaned it up... This is hard to find and will become quite a problem... A better way to tackle this is do null checks wherever necessary during the development process. This will save you a lot of time.

By finding by name I mean some framework allow you to FIndObjects using strings and the code might look like this: FindObject("ObjectName");

泪意 2025-01-25 19:05:01

当您尝试使用的类的对象未实例化时,NullReferenceException或对象引用未设置为对象的实例。
例如:

假设您有一个名为Student的课程。

public class Student
{
    private string FirstName;
    private string LastName;
    public string GetFullName()
    {
        return FirstName + LastName;
    }
}

现在,考虑一下您试图检索学生全名的另一堂课。

public class StudentInfo
{      
    public string GetStudentName()
    {
        Student s;
        string fullname = s.GetFullName();
        return fullname;
    }        
}

如以上代码所示,该语句
学生S - 仅声明学生类型的变量,请注意,此时尚未实例化学生班。
因此,当语句 s.getfullname()被执行时,它将抛出NullReferenceException。

NullReferenceException or Object reference not set to an instance of an object occurs when an object of the class you are trying to use is not instantiated.
For example:

Assume that you have a class named Student.

public class Student
{
    private string FirstName;
    private string LastName;
    public string GetFullName()
    {
        return FirstName + LastName;
    }
}

Now, consider another class where you are trying to retrieve the student's full name.

public class StudentInfo
{      
    public string GetStudentName()
    {
        Student s;
        string fullname = s.GetFullName();
        return fullname;
    }        
}

As seen in the above code, the statement
Student s - only declares the variable of type Student, note that the Student class is not instantiated at this point.
Hence, when the statement s.GetFullName() gets executed, it will throw the NullReferenceException.

尾戒 2025-01-25 19:05:01

从字面上看,修复nullReferenceExeption的最简单方法有两种方式。

如果您有一个gameObject,例如带有脚本的脚本和一个名为 rb (刚体)的变量,则该变量将在您启动游戏时以null开头。
这就是为什么您获得NullReferenceExeption的原因,因为计算机没有存储在该变量中的数据。

我将以一个刚性变量为例。
实际上,我们可以通过几种方式可以很容易地添加数据:

  1. 使用AddComponent&gt;向对象添加一个刚性体。物理&GT;僵化的身体
    然后进入您的脚本并键入rb = getComponent&lt; strigbody&gt;();
    这一行代码在您的start()awake()函数下工作。
  2. 您可以以编程方式添加组件,并同时使用一行代码分配变量:rb = addComponent&lt; strig&gt;();

进一步注释:如果您想要 unity 要在对象中添加一个组件,您可能已经忘记了一个,您可以键入一个[sirceseComponent (typeof(arigidbody))]在您的类声明上方(使用 s的所有下方的空间)。

享受并玩得开心!

Literally the easiest way to fix a NullReferenceExeption has two ways.

If you have a GameObject for example with a script attached and a variable named rb (rigidbody) this variable will start with null when you start your game.
This is why you get a NullReferenceExeption because the computer does not have data stored in that variable.

I'll be using a RigidBody variable as an example.
We can add data really easily actually in a few ways:

  1. Add a RigidBody to your object with AddComponent > Physics > Rigidbody
    Then go into your script and type rb = GetComponent<Rigidbody>();
    This line of code works best under your Start() or Awake() functions.
  2. You can add a component programmatically and assign the variable at the same time with one line of code: rb = AddComponent<RigidBody>();

Further Notes: If you want Unity to add a component to your object and you might have forgotten to add one, you can type [RequireComponent(typeof(RigidBody))] above your class declaration (the space below all of your usings).

Enjoy and have fun making games!

燕归巢 2025-01-25 19:05:01

这基本上是一个零参考异常。 AS microsoft> Microsoft

尝试访问一个NullReference Exception异常
值为null的类型的成员。

这意味着什么?

这意味着,如果任何不具有任何价值的成员,我们正在使该成员执行某些任务,那么该系统无疑会扔出消息,然后说 -

“嘿,等等,该成员没有值,因此无法 的任务。

执行您要交出 因此,这表示仅在使用参考类型作为值类型时才发生。

如果我们使用Value类型成员,则不会发生NullReferenceException。

class Program
{
    static void Main(string[] args)
    {
        string str = null;
        Console.WriteLine(str.Length);
        Console.ReadLine();
    }
}

上面的代码显示了用 null 值分配的简单字符串。

现在,当我尝试打印字符串的长度 str 时,我确实会出现 'system.nullReferenceException'的类型消息,因为成员 str 消息/strong>指向零,没有任何时间的空。

' nullReferenceException '当我们忘记实例化参考类型时,也会发生。

假设我有一个类和成员方法。我没有实例化我的班级,但只命名了我的班级。现在,如果我尝试使用该方法,编译器将发出错误或发出警告(取决于编译器)。

class Program
{
    static void Main(string[] args)
    {
        MyClass1 obj;
        obj.foo();  // Use of unassigned local variable 'obj'
    }
}

public class MyClass1
{
    internal void foo()
    {
        Console.WriteLine("Hello from foo");
    }
}

上述代码的编译器提出了一个错误,即变量 obj 未分配,这表明我们的变量具有零值或没有。上述代码的编译器提出了一个错误,即变量 obj 未分配,这表明我们的变量具有零值或没有。

为什么发生?

  • nullReferenceException由于我们没有检查对象的值而出现了。我们经常将对象值放在代码开发中未选中。

  • 当我们忘记实例化对象时,它也会出现。使用方法,属性,集合等可以返回或设置为空值的方法也可能是此例外的原因。

如何避免它?

有多种避免此著名例外的方法和方法:

  1. 明确检查:我们应该遵守检查对象,属性,方法,阵列和集合的传统,无论它们是否为无效。可以简单地使用条件语句(例如if-else if-else等)实现。

  2. 异常处理:管理此例外的重要方法之一)来实现这一点。使用简单的尝试键入块,我们可以控制此异常并保持其日志。当您的应用程序处于生产阶段时,这可能非常有用。

  3. null运算符:无效的合并操作员和无条件操作员也可以用方便地使用,同时将值设置为对象,变量,属性和字段。

  4. 调试器:对于开发人员来说,我们拥有与我们一起调试的重要武器。如果我们在开发面前面对NullReferenceException,我们可以使用调试器来达到例外的来源。

  5. 内置方法:诸如getValueordEfault(),isnullorWhitespace()和isnullorement()检查nulls的系统方法,如果有空值。

    ,请分配默认值。

这里已经有很多好的答案。您还可以在我的博客

希望这也有帮助!

This is basically is a Null reference exception. As Microsoft states-

A NullReferenceException exception is thrown when you try to access a
member of a type whose value is null.

What does that mean?

That means if any member which doesn’t hold any value and we are making that member to perform certain task then the system will undoubtedly toss a message and say-

“Hey wait, that member has no values so it can’t perform the task which you are handing it over.”

The exception itself says that something is being referred but whose value is not being set. So this denotes that it only occurs while using reference types as Value types are non-nullable.

NullReferenceException won't occur if we are using Value type members.

class Program
{
    static void Main(string[] args)
    {
        string str = null;
        Console.WriteLine(str.Length);
        Console.ReadLine();
    }
}

The above code shows simple string which is assigned with a null value.

Now, when I try to print the length of the string str, I do get An unhandled exception of type ‘System.NullReferenceException’ occurred message because member str is pointing to null and there can’t be any length of null.

NullReferenceException’ also occurs when we forget to instantiate a reference type.

Suppose I have a class and member method in it. I have not instantiated my class but only named my class. Now if I try to use the method, the compiler will throw an error or issue a warning (depending on the compiler).

class Program
{
    static void Main(string[] args)
    {
        MyClass1 obj;
        obj.foo();  // Use of unassigned local variable 'obj'
    }
}

public class MyClass1
{
    internal void foo()
    {
        Console.WriteLine("Hello from foo");
    }
}

Compiler for the above code raises an error that variable obj is unassigned which signifies that our variable has null values or nothing. Compiler for the above code raises an error that variable obj is unassigned which signifies that our variable has null values or nothing.

Why does it occur?

  • NullReferenceException arises due to our fault for not checking the object’s value. We often leave the object values unchecked in the code development.

  • It also arises when we forget to instantiate our objects. Using methods, properties, collections etc. which can return or set null values can also be the cause of this exception.

How can it be avoided?

There are various ways and methods to avoid this renowned exception:

  1. Explicit Checking: We should adhere to the tradition of checking the objects, properties, methods, arrays, and collections whether they are null. This can be simply implemented using conditional statements like if-else if-else etc.

  2. Exception handling: One of the important ways of managing this exception. Using simple try-catch-finally blocks we can control this exception and also maintain a log of it. This can be very useful when your application is on production stage.

  3. Null operators: Null Coalescing operator and null conditional operators can also be used in handy while setting values to objects, variables, properties and fields.

  4. Debugger: For developers, we have the big weapon of Debugging with us. If have we face NullReferenceException during the development face we can use the debugger to get to the source of the exception.

  5. Built-in method: System methods such as GetValueOrDefault(), IsNullOrWhiteSpace(), and IsNullorEmpty() checks for nulls and assign the default value if there is a null value.

There are many good answers already here. You can also check more detailed description with examples on my blog.

Hope this helps too!

情愿 2025-01-25 19:05:00

原因是什么?

底线

您正在尝试使用 null(或 VB.NET 中的 Nothing)的内容。这意味着您要么将其设置为 null,要么根本不将其设置为任何内容。

与其他任何东西一样,null 也会被传递。如果方法“A”中的值为 null ,则可能是方法“B”将 null 传递给了方法“A”。

null 可以有不同的含义:

  1. 未初始化的对象变量,因此指向任何内容。在这种情况下,如果您访问此类对象的成员,它会导致 NullReferenceException
  2. 开发人员有意使用null来表示没有可用的有意义的值。请注意,C# 具有变量可为空数据类型的概念(例如数据库表可以具有可为空字段) -您可以将 null 分配给它们以指示其中没有存储任何值,例如 int? a = null;(这是 Nullablea = null; 的快捷方式),其中问号表示允许在变量中存储 null 一个。您可以使用 if (a.HasValue) {...}if (a==null) {...} 进行检查。可空变量(如本示例中的 a)允许通过 a.Value 显式访问值,或者像平常一样通过 a 访问值。
    注意,如果,通过a.Value访问它会抛出InvalidOperationException而不是NullReferenceException anull - 您应该事先进行检查,即如果您有另一个不可为 null 的变量 int b; 那么您应该进行像 这样的赋值if (a.HasValue) { b = a.值; } 或更短的 if (a != null) { b = a; }

本文的其余部分将更详细地介绍许多程序员经常犯的错误,这些错误可能会导致 NullReferenceException

更具体地说,

runtime 抛出 NullReferenceException always 意味着同样的事情:您正在尝试使用引用,并且该引用未初始化(或者它曾经初始化过,但不再初始化)。

这意味着该引用为 null,并且您无法通过 null 引用访问成员(例如方法)。最简单的情况:

string foo = null;
foo.ToUpper();

这将在第二行抛出 NullReferenceException,因为您无法在 string 引用上调用实例方法 ToUpper()指向null

调试

如何找到 NullReferenceException 的来源?除了查看异常本身(异常将在异常发生的位置准确抛出)之外,Visual Studio 中的调试一般规则也适用:放置策略断点和 检查变量,方法是将鼠标悬停在变量名称上,打开(快速)监视窗口或使用各种调试面板,例如 Locals 和汽车。

如果您想找出引用的设置位置或未设置位置,请右键单击其名称并选择“查找所有引用”。然后,您可以在每个找到的位置放置一个断点,并使用附加的调试器运行程序。每次调试器在此类断点处中断时,您都需要确定是否希望引用为非空,检查变量,并验证它是否在您希望时指向实例。

通过这种方式遵循程序流程,您可以找到实例不应该为空的位置,以及为什么没有正确设置它。

示例

一些可能引发异常的常见场景:

通用

ref1.ref2.ref3.member

如果 ref1 或 ref2 或 ref3 为 null,那么您将收到 NullReferenceException。如果您想解决该问题,请通过将表达式重写为其更简单的等效项来找出哪个为 null:

var r1 = ref1;
var r2 = r1.ref2;
var r3 = r2.ref3;
r3.member

具体来说,在 HttpContext.Current.User.Identity.Name 中,HttpContext. Current 可以为 null,或者 User 属性可以为 null,或者 Identity 属性可以为 null。

间接

public class Person 
{
    public int Age { get; set; }
}
public class Book 
{
    public Person Author { get; set; }
}
public class Example 
{
    public void Foo() 
    {
        Book b1 = new Book();
        int authorAge = b1.Author.Age; // You never initialized the Author property.
                                       // There is no Person to get an Age from.
    }
}

如果您想避免子(Person)空引用,您可以在父(Book)对象的构造函数中初始化它。

嵌套对象初始值设定项

同样适用于嵌套对象初始值设定项:

Book b1 = new Book 
{ 
   Author = { Age = 45 } 
};

这意味着:

Book b1 = new Book();
b1.Author.Age = 45;

使用 new 关键字时,它仅创建 Book 的新实例,而不是新实例Person,因此 Author 属性仍为 null

嵌套集合初始值设定

public class Person 
{
    public ICollection<Book> Books { get; set; }
}
public class Book 
{
    public string Title { get; set; }
}

项 嵌套集合 Initializers 的行为相同:

Person p1 = new Person 
{
    Books = {
         new Book { Title = "Title1" },
         new Book { Title = "Title2" },
    }
};

这意味着:

Person p1 = new Person();
p1.Books.Add(new Book { Title = "Title1" });
p1.Books.Add(new Book { Title = "Title2" });

new Person 仅创建 Person 的实例,但 >Books 集合仍为 null。集合 Initializer 语法不会创建集合
对于 p1.Books,它仅转换为 p1.Books.Add(...) 语句。

数组

int[] numbers = null;
int n = numbers[0]; // numbers is null. There is no array to index.

数组元素

Person[] people = new Person[5];
people[0].Age = 20 // people[0] is null. The array was allocated but not
                   // initialized. There is no Person to set the Age for.

交错数组

long[][] array = new long[1][];
array[0][0] = 3; // is null because only the first dimension is yet initialized.
                 // Use array[0] = new long[2]; first.

集合/列表/字典

Dictionary<string, int> agesForNames = null;
int age = agesForNames["Bob"]; // agesForNames is null.
                               // There is no Dictionary to perform the lookup.

范围 变量(间接/延迟)

public class Person 
{
    public string Name { get; set; }
}
var people = new List<Person>();
people.Add(null);
var names = from p in people select p.Name;
string firstName = names.First(); // Exception is thrown here, but actually occurs
                                  // on the line above.  "p" is null because the
                                  // first element we added to the list is null.

事件 (C#)

public class Demo
{
    public event EventHandler StateChanged;
    
    protected virtual void OnStateChanged(EventArgs e)
    {        
        StateChanged(this, e); // Exception is thrown here 
                               // if no event handlers have been attached
                               // to StateChanged event
    }
}

(注意:VB.NET 编译器插入对事件使用情况的空检查,因此无需检查事件是否无任何内容 code> 在 VB.NET 中。)

错误的命名约定:

如果您对字段的命名与本地字段的命名不同,您可能会意识到您从未初始化过该字段。

public class Form1
{
    private Customer customer;
    
    private void Form1_Load(object sender, EventArgs e) 
    {
        Customer customer = new Customer();
        customer.Name = "John";
    }
    
    private void Button_Click(object sender, EventArgs e)
    {
        MessageBox.Show(customer.Name);
    }
}

这可以通过遵循以下划线前缀字段的约定来解决:

    private Customer _customer;

ASP.NET 页面生命周期:

public partial class Issues_Edit : System.Web.UI.Page
{
    protected TestIssue myIssue;

    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
             // Only called on first load, not when button clicked
             myIssue = new TestIssue(); 
        }
    }
        
    protected void SaveButton_Click(object sender, EventArgs e)
    {
        myIssue.Entry = "NullReferenceException here!";
    }
}

ASP.NET 会话值

// if the "FirstName" session value has not yet been set,
// then this line will throw a NullReferenceException
string firstName = Session["FirstName"].ToString();

ASP.NET MVC 空视图模型

如果引用 @ModelASP.NET MVC View 中,您需要了解当您返回视图时,Model 会在您的操作方法中设置。当您从控制器返回空模型(或模型属性)时,视图访问它时会发生异常:

// Controller
public class Restaurant:Controller
{
    public ActionResult Search()
    {
        return View();  // Forgot the provide a Model here.
    }
}

// Razor view 
@foreach (var restaurantSearch in Model.RestaurantSearch)  // Throws.
{
}
    
<p>@Model.somePropertyName</p> <!-- Also throws -->

WPF 控件创建顺序和事件

WPF 控件在调用 InitializeComponent< 期间创建/code> 按照它们在可视化树中出现的顺序。如果早期创建的控件具有事件处理程序等,并且在引用后期创建的控件的 InitializeComponent 期间触发,则会引发 NullReferenceException

例如:

<Grid>
    <!-- Combobox declared first -->
    <ComboBox Name="comboBox1" 
              Margin="10"
              SelectedIndex="0" 
              SelectionChanged="comboBox1_SelectionChanged">
       <ComboBoxItem Content="Item 1" />
       <ComboBoxItem Content="Item 2" />
       <ComboBoxItem Content="Item 3" />
    </ComboBox>
        
    <!-- Label declared later -->
    <Label Name="label1" 
           Content="Label"
           Margin="10" />
</Grid>

这里comboBox1是在label1之前创建的。如果 comboBox1_SelectionChanged 尝试引用 label1,则它尚未创建。

private void comboBox1_SelectionChanged(object sender, SelectionChangedEventArgs e)
{
    label1.Content = comboBox1.SelectedIndex.ToString(); // NullReferenceException here!!
}

更改 XAML 中声明的顺序(即,在 comboBox1 之前列出 label1,忽略设计理念问题)至少可以解决 <代码>NullReferenceException在这里。

使用 as 进行强制转换

var myThing = someObject as Thing;

这不会引发 InvalidCastException,但在强制转换失败时(以及当 someObject 时)返回 null本身为空)。所以要注意这一点。

LINQ FirstOrDefault()SingleOrDefault()

普通版本 First()Single() 会在出现异常时抛出异常没什么。在这种情况下,“OrDefault”版本返回 null。所以要注意这一点。

foreach

当您尝试迭代 null 集合时, foreach 会抛出异常。通常是由返回集合的方法产生意外的 null 结果引起的。

List<int> list = null;    
foreach(var v in list) { } // NullReferenceException here

更实际的示例 - 从 XML 文档中选择节点。如果未找到节点但初始调试显示所有属性均有效,则会抛出异常:

foreach (var node in myData.MyXml.DocumentNode.SelectNodes("//Data"))

的方法

避免显式检查 null 并忽略 null

。如果您预计引用有时为 null,则可以在访问实例成员之前检查它是否为 null

void PrintName(Person p)
{
    if (p != null) 
    {
        Console.WriteLine(p.Name);
    }
}

显式检查 null 并提供默认值。

您调用的期望实例的方法可能会返回 null,例如,当无法找到正在查找的对象时。在这种情况下,您可以选择返回默认值:

string GetCategory(Book b) 
{
    if (b == null)
        return "Unknown";
    return b.Category;
}

从方法调用中显式检查 null 并引发自定义异常。

您还可以抛出自定义异常,仅在调用代码中捕获它:

string GetCategory(string bookTitle) 
{
    var book = library.FindBook(bookTitle);  // This may return null
    if (book == null)
        throw new BookNotFoundException(bookTitle);  // Your custom exception
    return book.Category;
}

如果值永远不应该为 null,请使用 Debug.Assert,以便在出现问题之前捕获问题。发生异常。

如果您在开发过程中知道某个方法可以但永远不应该返回 null,则可以使用 Debug.Assert() 在它确实发生时尽快中断

string GetTitle(int knownBookID) 
{
    // You know this should never return null.
    var book = library.GetBook(knownBookID);  

    // Exception will occur on the next line instead of at the end of this method.
    Debug.Assert(book != null, "Library didn't return a book for known book ID.");

    // Some other code

    return book.Title; // Will never throw NullReferenceException in Debug mode.
}

:此检查不会最终出现在您的发布版本中,导致它抛出在发布模式下运行时,当 book == null 时再次出现 NullReferenceException

可为 null 值类型使用 GetValueOrDefault(),以便在它们为 null 时提供默认值。

DateTime? appointment = null;
Console.WriteLine(appointment.GetValueOrDefault(DateTime.Now));
// Will display the default value provided (DateTime.Now), because appointment is null.

appointment = new DateTime(2022, 10, 20);
Console.WriteLine(appointment.GetValueOrDefault(DateTime.Now));
// Will display the appointment date, not the default

使用空合并运算符:?? [C#] 或 If() [VB]。

遇到 null 时提供默认值的简写:

IService CreateService(ILogger log, Int32? frobPowerLevel)
{
   var serviceImpl = new MyService(log ?? NullLog.Instance);
 
   // Note that the above "GetValueOrDefault()" can also be rewritten to use
   // the coalesce operator:
   serviceImpl.FrobPowerLevel = frobPowerLevel ?? 5;
}

对数组使用 null 条件运算符:?.?[x] (在 C# 6 和 VB.NET 14 中可用):

有时也称为安全导航或 Elvis(以其形状命名)运算符。如果运算符左侧的表达式为 null,则不会计算右侧,而是返回 null。这意味着像这样的情况:

var title = person.Title.ToUpper();

如果此人没有头衔,则会抛出异常,因为它试图对具有 null 值的属性调用 ToUpper

在 C# 5 及以下版本中,可以通过以下方式进行保护:

var title = person.Title == null ? null : person.Title.ToUpper();

现在 title 变量将为 null,而不是引发异常。 C# 6 为此引入了更短的语法:

var title = person.Title?.ToUpper();

这将导致 title 变量为 null,并且如果 person.Title 则不会调用 ToUpper code> 为 null

当然,您仍然必须检查 title 是否为 null 或将 null 条件运算符与 null 合并运算符一起使用 (??)来提供默认值:

// regular null check
int titleLength = 0;
if (title != null)
    titleLength = title.Length; // If title is null, this would throw NullReferenceException
    
// combining the `?` and the `??` operator
int titleLength = title?.Length ?? 0;

同样,对于数组,您可以使用 ?[i],如下所示:

int[] myIntArray = null;
var i = 5;
int? elem = myIntArray?[i];
if (!elem.HasValue) Console.WriteLine("No value");

这将执行以下操作:如果 myIntArraynull,表达式返回 null 并且您可以安全地检查它。如果它包含一个数组,它将执行以下操作:
elem = myIntArray[i]; 并返回第 ith 元素。

使用 null 上下文(在 C# 8 中可用):

C# 8 中引入,null 上下文和可为 null 的引用类型对变量执行静态分析,并在值可能为 null时提供编译器警告code> 或已设置为 null。可空引用类型允许显式允许类型为null

可以使用 csproj 文件中的 Nullable 元素为项目设置可为空注释上下文和可为空警告上下文。此元素配置编译器如何解释类​​型的可为空性以及生成哪些警告。有效设置为:

  • enable:启用可为空注释上下文。可以为空的警告上下文已启用。引用类型(例如字符串)的变量是不可为 null 的。所有可空性警告均已启用。
  • disable:可空注释上下文被禁用。可为空的警告上下文已禁用。引用类型的变量是不可见的,就像 C# 的早期版本一样。所有可空性警告均被禁用。
  • safeonly:启用可空注释上下文。可为空的警告上下文是安全的。引用类型的变量不可为空。所有安全可空性警告均已启用。
  • 警告:可空注释上下文已禁用。可以为空的警告上下文已启用。引用类型的变量是不可见的。所有可空性警告均已启用。
  • safeonlywarnings:可空注释上下文已禁用。可为空的警告上下文是安全的。
    引用类型的变量是不可见的。所有安全可空性警告均已启用。

可空引用类型使用与可为空值类型相同的语法进行标记:将 ? 附加到变量的类型。

用于调试和修复迭代器中空解引用的特殊技术

C# 支持“迭代器块”(在其他一些流行语言中称为“生成器”)。由于延迟执行,NullReferenceException 在迭代器块中调试可能特别棘手:

public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
    for (int i = 0; i < count; ++i)
    yield return f.MakeFrob();
}
...
FrobFactory factory = whatever;
IEnumerable<Frobs> frobs = GetFrobs();
...
foreach(Frob frob in frobs) { ... }

如果 whatever 结果为 null,则 MakeFrob会抛出。现在,您可能认为正确的做法是:

// DON'T DO THIS
public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
   if (f == null) 
      throw new ArgumentNullException("f", "factory must not be null");
   for (int i = 0; i < count; ++i)
      yield return f.MakeFrob();
}

为什么这是错误的?因为迭代器块直到 foreach 才真正运行!对 GetFrobs 的调用只是返回一个对象,该对象在迭代时将运行迭代器块。

通过像这样编写 null 检查,您可以防止出现 NullReferenceException,但可以将 NullArgumentException 移动到迭代点 >,没有达到调用的程度,这调试起来非常混乱

正确的修复方法是:

// DO THIS
public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
   // No yields in a public method that throws!
   if (f == null) 
       throw new ArgumentNullException("f", "factory must not be null");
   return GetFrobsForReal(f, count);
}
private IEnumerable<Frob> GetFrobsForReal(FrobFactory f, int count)
{
   // Yields in a private method
   Debug.Assert(f != null);
   for (int i = 0; i < count; ++i)
        yield return f.MakeFrob();
}

也就是说,创建一个具有迭代器块逻辑的私有帮助器方法和一个执行 null 检查并返回迭代器的公共表面方法。现在,当调用 GetFrobs 时,null 检查立即发生,然后在迭代序列时执行 GetFrobsForReal

如果您检查LINQ to Objects 的参考源,您将发现该技术自始至终都在使用。它写起来稍微有点笨拙,但它使调试无效错误变得更加容易。 优化代码是为了调用者的方便,而不是为了作者的方便

关于不安全代码中的 null 取消引用的说明

C# 有一种“不安全”模式,顾名思义,这种模式极其危险,因为提供内存安全和类型安全的正常安全机制并未强制执行。 除非您对内存的工作原理有透彻而深入的了解,否则不应编写不安全的代码

在不安全模式下,您应该了解两个重要事实:

  • 取消引用空指针 会产生与取消引用空引用 相同的异常
  • 取消引用无效的非空指针在某些情况下可能会产生该异常。

要了解其原因,首先需要了解 .NET 如何产生 NullReferenceException。 (这些详细信息适用于在 Windows 上运行的 .NET;其他操作系统使用类似的机制。)

Windows 中的内存是虚拟化的;每个进程都会获得由操作系统跟踪的许多内存“页”组成的虚拟内存空间。内存的每个页面上都设置了标志,用于确定如何使用它:读取、写入、执行等。 最低页面被标记为“如果以任何方式使用都会产生错误”。

C# 中的空指针和空引用在内部都表示为数字零,因此任何将其取消引用到其相应内存存储的尝试都会导致操作系统产生错误。然后 .NET 运行时会检测到此错误并将其转换为 NullReferenceException。

这就是为什么取消引用空指针和空引用会产生相同的异常。

那么第二点呢?取消引用位于虚拟内存最低页中的任何无效指针都会导致相同的操作系统错误,从而导致相同的异常。

为什么这是有道理的?好吧,假设我们有一个包含两个 int 的结构,以及一个等于 null 的非托管指针。如果我们尝试取消引用结构中的第二个 int,CLR 将不会尝试访问位置 0 处的存储;它将访问位置四的存储。但从逻辑上讲,这是一个 null 取消引用,因为我们通过 null 访问该地址。

如果您正在使用不安全的代码并且收到 NullReferenceException,请注意有问题的指针不必为 null。可以是最底层页面的任意位置,都会产生该异常。

What is the cause?

Bottom Line

You are trying to use something that is null (or Nothing in VB.NET). This means you either set it to null, or you never set it to anything at all.

Like anything else, null gets passed around. If it is null in method "A", it could be that method "B" passed a null to method "A".

null can have different meanings:

  1. Object variables that are uninitialized and hence point to nothing. In this case, if you access members of such objects, it causes a NullReferenceException.
  2. The developer is using null intentionally to indicate there is no meaningful value available. Note that C# has the concept of nullable datatypes for variables (like database tables can have nullable fields) - you can assign null to them to indicate there is no value stored in it, for example int? a = null; (which is a shortcut for Nullable<int> a = null;) where the question mark indicates it is allowed to store null in variable a. You can check that either with if (a.HasValue) {...} or with if (a==null) {...}. Nullable variables, like a in this example, allow to access the value via a.Value explicitly, or just as normal via a.
    Note that accessing it via a.Value throws an InvalidOperationException instead of a NullReferenceException if a is null - you should do the check beforehand, i.e. if you have another non-nullable variable int b; then you should do assignments like if (a.HasValue) { b = a.Value; } or shorter if (a != null) { b = a; }.

The rest of this article goes into more detail and shows mistakes that many programmers often make which can lead to a NullReferenceException.

More Specifically

The runtime throwing a NullReferenceException always means the same thing: you are trying to use a reference, and the reference is not initialized (or it was once initialized, but is no longer initialized).

This means the reference is null, and you cannot access members (such as methods) through a null reference. The simplest case:

string foo = null;
foo.ToUpper();

This will throw a NullReferenceException at the second line because you can't call the instance method ToUpper() on a string reference pointing to null.

Debugging

How do you find the source of a NullReferenceException? Apart from looking at the exception itself, which will be thrown exactly at the location where it occurs, the general rules of debugging in Visual Studio apply: place strategic breakpoints and inspect your variables, either by hovering the mouse over their names, opening a (Quick)Watch window or using the various debugging panels like Locals and Autos.

If you want to find out where the reference is or isn't set, right-click its name and select "Find All References". You can then place a breakpoint at every found location and run your program with the debugger attached. Every time the debugger breaks on such a breakpoint, you need to determine whether you expect the reference to be non-null, inspect the variable, and verify that it points to an instance when you expect it to.

By following the program flow this way, you can find the location where the instance should not be null, and why it isn't properly set.

Examples

Some common scenarios where the exception can be thrown:

Generic

ref1.ref2.ref3.member

If ref1 or ref2 or ref3 is null, then you'll get a NullReferenceException. If you want to solve the problem, then find out which one is null by rewriting the expression to its simpler equivalent:

var r1 = ref1;
var r2 = r1.ref2;
var r3 = r2.ref3;
r3.member

Specifically, in HttpContext.Current.User.Identity.Name, the HttpContext.Current could be null, or the User property could be null, or the Identity property could be null.

Indirect

public class Person 
{
    public int Age { get; set; }
}
public class Book 
{
    public Person Author { get; set; }
}
public class Example 
{
    public void Foo() 
    {
        Book b1 = new Book();
        int authorAge = b1.Author.Age; // You never initialized the Author property.
                                       // There is no Person to get an Age from.
    }
}

If you want to avoid the child (Person) null reference, you could initialize it in the parent (Book) object's constructor.

Nested Object Initializers

The same applies to nested object initializers:

Book b1 = new Book 
{ 
   Author = { Age = 45 } 
};

This translates to:

Book b1 = new Book();
b1.Author.Age = 45;

While the new keyword is used, it only creates a new instance of Book, but not a new instance of Person, so the Author property is still null.

Nested Collection Initializers

public class Person 
{
    public ICollection<Book> Books { get; set; }
}
public class Book 
{
    public string Title { get; set; }
}

The nested collection Initializers behave the same:

Person p1 = new Person 
{
    Books = {
         new Book { Title = "Title1" },
         new Book { Title = "Title2" },
    }
};

This translates to:

Person p1 = new Person();
p1.Books.Add(new Book { Title = "Title1" });
p1.Books.Add(new Book { Title = "Title2" });

The new Person only creates an instance of Person, but the Books collection is still null. The collection Initializer syntax does not create a collection
for p1.Books, it only translates to the p1.Books.Add(...) statements.

Array

int[] numbers = null;
int n = numbers[0]; // numbers is null. There is no array to index.

Array Elements

Person[] people = new Person[5];
people[0].Age = 20 // people[0] is null. The array was allocated but not
                   // initialized. There is no Person to set the Age for.

Jagged Arrays

long[][] array = new long[1][];
array[0][0] = 3; // is null because only the first dimension is yet initialized.
                 // Use array[0] = new long[2]; first.

Collection/List/Dictionary

Dictionary<string, int> agesForNames = null;
int age = agesForNames["Bob"]; // agesForNames is null.
                               // There is no Dictionary to perform the lookup.

Range Variable (Indirect/Deferred)

public class Person 
{
    public string Name { get; set; }
}
var people = new List<Person>();
people.Add(null);
var names = from p in people select p.Name;
string firstName = names.First(); // Exception is thrown here, but actually occurs
                                  // on the line above.  "p" is null because the
                                  // first element we added to the list is null.

Events (C#)

public class Demo
{
    public event EventHandler StateChanged;
    
    protected virtual void OnStateChanged(EventArgs e)
    {        
        StateChanged(this, e); // Exception is thrown here 
                               // if no event handlers have been attached
                               // to StateChanged event
    }
}

(Note: The VB.NET compiler inserts null checks for event usage, so it's not necessary to check events for Nothing in VB.NET.)

Bad Naming Conventions:

If you named fields differently from locals, you might have realized that you never initialized the field.

public class Form1
{
    private Customer customer;
    
    private void Form1_Load(object sender, EventArgs e) 
    {
        Customer customer = new Customer();
        customer.Name = "John";
    }
    
    private void Button_Click(object sender, EventArgs e)
    {
        MessageBox.Show(customer.Name);
    }
}

This can be solved by following the convention to prefix fields with an underscore:

    private Customer _customer;

ASP.NET Page Life cycle:

public partial class Issues_Edit : System.Web.UI.Page
{
    protected TestIssue myIssue;

    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
             // Only called on first load, not when button clicked
             myIssue = new TestIssue(); 
        }
    }
        
    protected void SaveButton_Click(object sender, EventArgs e)
    {
        myIssue.Entry = "NullReferenceException here!";
    }
}

ASP.NET Session Values

// if the "FirstName" session value has not yet been set,
// then this line will throw a NullReferenceException
string firstName = Session["FirstName"].ToString();

ASP.NET MVC empty view models

If the exception occurs when referencing a property of @Model in an ASP.NET MVC View, you need to understand that the Model gets set in your action method, when you return a view. When you return an empty model (or model property) from your controller, the exception occurs when the views access it:

// Controller
public class Restaurant:Controller
{
    public ActionResult Search()
    {
        return View();  // Forgot the provide a Model here.
    }
}

// Razor view 
@foreach (var restaurantSearch in Model.RestaurantSearch)  // Throws.
{
}
    
<p>@Model.somePropertyName</p> <!-- Also throws -->

WPF Control Creation Order and Events

WPF controls are created during the call to InitializeComponent in the order they appear in the visual tree. A NullReferenceException will be raised in the case of early-created controls with event handlers, etc., that fire during InitializeComponent which reference late-created controls.

For example:

<Grid>
    <!-- Combobox declared first -->
    <ComboBox Name="comboBox1" 
              Margin="10"
              SelectedIndex="0" 
              SelectionChanged="comboBox1_SelectionChanged">
       <ComboBoxItem Content="Item 1" />
       <ComboBoxItem Content="Item 2" />
       <ComboBoxItem Content="Item 3" />
    </ComboBox>
        
    <!-- Label declared later -->
    <Label Name="label1" 
           Content="Label"
           Margin="10" />
</Grid>

Here comboBox1 is created before label1. If comboBox1_SelectionChanged attempts to reference label1, it will not yet have been created.

private void comboBox1_SelectionChanged(object sender, SelectionChangedEventArgs e)
{
    label1.Content = comboBox1.SelectedIndex.ToString(); // NullReferenceException here!!
}

Changing the order of the declarations in the XAML (i.e., listing label1 before comboBox1, ignoring issues of design philosophy) would at least resolve the NullReferenceException here.

Cast with as

var myThing = someObject as Thing;

This doesn't throw an InvalidCastException but returns a null when the cast fails (and when someObject is itself null). So be aware of that.

LINQ FirstOrDefault() and SingleOrDefault()

The plain versions First() and Single() throw exceptions when there is nothing. The "OrDefault" versions return null in that case. So be aware of that.

foreach

foreach throws when you try to iterate on a null collection. Usually caused by unexpected null result from methods that return collections.

List<int> list = null;    
foreach(var v in list) { } // NullReferenceException here

More realistic example - select nodes from XML document. Will throw if nodes are not found but initial debugging shows that all properties valid:

foreach (var node in myData.MyXml.DocumentNode.SelectNodes("//Data"))

Ways to Avoid

Explicitly check for null and ignore null values.

If you expect the reference sometimes to be null, you can check for it being null before accessing instance members:

void PrintName(Person p)
{
    if (p != null) 
    {
        Console.WriteLine(p.Name);
    }
}

Explicitly check for null and provide a default value.

Methods you call expecting an instance can return null, for example when the object being sought cannot be found. You can choose to return a default value when this is the case:

string GetCategory(Book b) 
{
    if (b == null)
        return "Unknown";
    return b.Category;
}

Explicitly check for null from method calls and throw a custom exception.

You can also throw a custom exception, only to catch it in the calling code:

string GetCategory(string bookTitle) 
{
    var book = library.FindBook(bookTitle);  // This may return null
    if (book == null)
        throw new BookNotFoundException(bookTitle);  // Your custom exception
    return book.Category;
}

Use Debug.Assert if a value should never be null, to catch the problem earlier than the exception occurs.

When you know during development that a method could, but never should return null, you can use Debug.Assert() to break as soon as possible when it does occur:

string GetTitle(int knownBookID) 
{
    // You know this should never return null.
    var book = library.GetBook(knownBookID);  

    // Exception will occur on the next line instead of at the end of this method.
    Debug.Assert(book != null, "Library didn't return a book for known book ID.");

    // Some other code

    return book.Title; // Will never throw NullReferenceException in Debug mode.
}

Though this check will not end up in your release build, causing it to throw the NullReferenceException again when book == null at runtime in release mode.

Use GetValueOrDefault() for nullable value types to provide a default value when they are null.

DateTime? appointment = null;
Console.WriteLine(appointment.GetValueOrDefault(DateTime.Now));
// Will display the default value provided (DateTime.Now), because appointment is null.

appointment = new DateTime(2022, 10, 20);
Console.WriteLine(appointment.GetValueOrDefault(DateTime.Now));
// Will display the appointment date, not the default

Use the null coalescing operator: ?? [C#] or If() [VB].

The shorthand to providing a default value when a null is encountered:

IService CreateService(ILogger log, Int32? frobPowerLevel)
{
   var serviceImpl = new MyService(log ?? NullLog.Instance);
 
   // Note that the above "GetValueOrDefault()" can also be rewritten to use
   // the coalesce operator:
   serviceImpl.FrobPowerLevel = frobPowerLevel ?? 5;
}

Use the null condition operator: ?. or ?[x] for arrays (available in C# 6 and VB.NET 14):

This is also sometimes called the safe navigation or Elvis (after its shape) operator. If the expression on the left side of the operator is null, then the right side will not be evaluated, and null is returned instead. That means cases like this:

var title = person.Title.ToUpper();

If the person does not have a title, this will throw an exception because it is trying to call ToUpper on a property with a null value.

In C# 5 and below, this can be guarded with:

var title = person.Title == null ? null : person.Title.ToUpper();

Now the title variable will be null instead of throwing an exception. C# 6 introduces a shorter syntax for this:

var title = person.Title?.ToUpper();

This will result in the title variable being null, and the call to ToUpper is not made if person.Title is null.

Of course, you still have to check title for null or use the null condition operator together with the null coalescing operator (??) to supply a default value:

// regular null check
int titleLength = 0;
if (title != null)
    titleLength = title.Length; // If title is null, this would throw NullReferenceException
    
// combining the `?` and the `??` operator
int titleLength = title?.Length ?? 0;

Likewise, for arrays you can use ?[i] as follows:

int[] myIntArray = null;
var i = 5;
int? elem = myIntArray?[i];
if (!elem.HasValue) Console.WriteLine("No value");

This will do the following: If myIntArray is null, the expression returns null and you can safely check it. If it contains an array, it will do the same as:
elem = myIntArray[i]; and returns the ith element.

Use null context (available in C# 8):

Introduced in C# 8, null contexts and nullable reference types perform static analysis on variables and provide a compiler warning if a value can be potentially null or have been set to null. The nullable reference types allow types to be explicitly allowed to be null.

The nullable annotation context and nullable warning context can be set for a project using the Nullable element in your csproj file. This element configures how the compiler interprets the nullability of types and what warnings are generated. Valid settings are:

  • enable: The nullable annotation context is enabled. The nullable warning context is enabled. Variables of a reference type, string, for example, are non-nullable. All nullability warnings are enabled.
  • disable: The nullable annotation context is disabled. The nullable warning context is disabled. Variables of a reference type are oblivious, just like earlier versions of C#. All nullability warnings are disabled.
  • safeonly: The nullable annotation context is enabled. The nullable warning context is safeonly. Variables of a reference type are non-nullable. All safety nullability warnings are enabled.
  • warnings: The nullable annotation context is disabled. The nullable warning context is enabled. Variables of a reference type are oblivious. All nullability warnings are enabled.
  • safeonlywarnings: The nullable annotation context is disabled. The nullable warning context is safeonly.
    Variables of a reference type are oblivious. All safety nullability warnings are enabled.

A nullable reference type is noted using the same syntax as nullable value types: a ? is appended to the type of the variable.

Special techniques for debugging and fixing null derefs in iterators

C# supports "iterator blocks" (called "generators" in some other popular languages). NullReferenceException can be particularly tricky to debug in iterator blocks because of deferred execution:

public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
    for (int i = 0; i < count; ++i)
    yield return f.MakeFrob();
}
...
FrobFactory factory = whatever;
IEnumerable<Frobs> frobs = GetFrobs();
...
foreach(Frob frob in frobs) { ... }

If whatever results in null then MakeFrob will throw. Now, you might think that the right thing to do is this:

// DON'T DO THIS
public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
   if (f == null) 
      throw new ArgumentNullException("f", "factory must not be null");
   for (int i = 0; i < count; ++i)
      yield return f.MakeFrob();
}

Why is this wrong? Because the iterator block does not actually run until the foreach! The call to GetFrobs simply returns an object which when iterated will run the iterator block.

By writing a null check like this you prevent the NullReferenceException, but you move the NullArgumentException to the point of the iteration, not to the point of the call, and that is very confusing to debug.

The correct fix is:

// DO THIS
public IEnumerable<Frob> GetFrobs(FrobFactory f, int count)
{
   // No yields in a public method that throws!
   if (f == null) 
       throw new ArgumentNullException("f", "factory must not be null");
   return GetFrobsForReal(f, count);
}
private IEnumerable<Frob> GetFrobsForReal(FrobFactory f, int count)
{
   // Yields in a private method
   Debug.Assert(f != null);
   for (int i = 0; i < count; ++i)
        yield return f.MakeFrob();
}

That is, make a private helper method that has the iterator block logic and a public surface method that does the null check and returns the iterator. Now when GetFrobs is called, the null check happens immediately, and then GetFrobsForReal executes when the sequence is iterated.

If you examine the reference source for LINQ to Objects you will see that this technique is used throughout. It is slightly more clunky to write, but it makes debugging nullity errors much easier. Optimize your code for the convenience of the caller, not the convenience of the author.

A note on null dereferences in unsafe code

C# has an "unsafe" mode which is, as the name implies, extremely dangerous because the normal safety mechanisms which provide memory safety and type safety are not enforced. You should not be writing unsafe code unless you have a thorough and deep understanding of how memory works.

In unsafe mode, you should be aware of two important facts:

  • dereferencing a null pointer produces the same exception as dereferencing a null reference
  • dereferencing an invalid non-null pointer can produce that exception in some circumstances

To understand why that is, it helps to understand how .NET produces NullReferenceException in the first place. (These details apply to .NET running on Windows; other operating systems use similar mechanisms.)

Memory is virtualized in Windows; each process gets a virtual memory space of many "pages" of memory that are tracked by the operating system. Each page of memory has flags set on it that determine how it may be used: read from, written to, executed, and so on. The lowest page is marked as "produce an error if ever used in any way".

Both a null pointer and a null reference in C# are internally represented as the number zero, and so any attempt to dereference it into its corresponding memory storage causes the operating system to produce an error. The .NET runtime then detects this error and turns it into the NullReferenceException.

That's why dereferencing both a null pointer and a null reference produces the same exception.

What about the second point? Dereferencing any invalid pointer that falls in the lowest page of virtual memory causes the same operating system error, and thereby the same exception.

Why does this make sense? Well, suppose we have a struct containing two ints, and an unmanaged pointer equal to null. If we attempt to dereference the second int in the struct, the CLR will not attempt to access the storage at location zero; it will access the storage at location four. But logically this is a null dereference because we are getting to that address via the null.

If you are working with unsafe code and you get a NullReferenceException, just be aware that the offending pointer need not be null. It can be any location in the lowest page, and this exception will be produced.

触ぅ动初心 2025-01-25 19:05:00

nullReference异常 - 视觉基本

nullReference异常 Visual Basic c#中的一个没有什么不同。毕竟,他们都报告了他们俩使用的.NET框架中定义的相同例外。视觉基础所独有的原因是罕见的(也许只有一个)。

该答案将使用视觉基本术语,语法和上下文。使用的示例来自大量过去的堆栈&nbsp;溢出问题。这是通过使用帖子中经常看到的情况的种类来最大化相关性。还为可能需要它的人提供了更多解释。与您类似的示例是非常可能在此处列出的示例。

注意:

  1. 这是基于概念的:没有代码可以粘贴到项目中。它旨在帮助您了解导致nullReferenceException(NRE),如何找到它,如何修复它以及如何避免它的原因。 NRE可以引起多种方式,因此这不太可能成为您的唯一遇到。
  2. 示例(来自Stack&nbsp; Overflow帖子)首先并不总是显示出做某事的最佳方法。
  3. 通常,使用最简单的补救措施。

基本含义

消息“对象未设置为对象实例” 表示您正在尝试使用尚未初始化的对象。这归结为其中之一:

  • 您的代码声明是对象变量,但它没有 inatialize it(创建一个实例或' instantiate '它)
  • 您的代码假设会初始化对象的某些东西,
  • 其他代码不可能过早地无效仍在使用的对象

找到原因

,因为问题是note nothere 检查他们以找出哪一个。然后确定为什么不初始化。将鼠标固定在各种变量上,Visual Studio(VS)将显示其值 - 罪魁祸首将为Nothing

“

您还应该从相关代码中删除任何尝试/捕获块堵塞。这将导致您的代码尝试使用nothing的对象时崩溃。 这就是您想要的,因为它将标识问题的精确位置,并允许您识别引起它的对象。

msgbox在捕获量中显示错误,而...几乎没有帮助。此方法还导致非常糟糕的 stack&nbsp;溢出问题,因为您无法描述实际例外,涉及的对象甚至代码行的发生在哪里。

您还可以使用当地窗口 debug - &gt; windows - &gt;当地人)检查您的对象。

一旦您知道问题所在,通常比发布一个新问题相当容易修复和更快。

另请参阅:

例外

http://msdn.microsoft.com/en-us/library/seyhszts(v=vs.110).aspx“ rel =“ noreferrer”> msdn : 一个实例

Dim reg As CashRegister
...
TextBox1.Text = reg.Amount         ' NRE

dim不创建CashRegister 对象;它仅声明该类型的名为reg的变量。 声明一个对象变量和创建实例是两种不同的事情。

补救件

通常可以使用运算符来创建实例时:

Dim reg As New CashRegister        ' [New] creates instance, invokes the constructor

' Longer, more explicit form:
Dim reg As CashRegister = New CashRegister

当仅适用于以后创建实例时:

Private reg As CashRegister         ' Declare
  ...
reg = New CashRegister()            ' Create instance

注意: do not < /strong>使用dim在一个过程中再次,包括构造函数(sub new):

Private reg As CashRegister
'...

Public Sub New()
   '...
   Dim reg As New CashRegister
End Sub

这将创建 local variable,reg,仅在此上下文(sub)中存在。 reg带模块级别的变量范围您将在其他任何地方使用nothing

缺少操作员是nullReference异常的#1原因 在stack&nbsp;溢出问题审查。

Visual Basic尝试使用 new :使用 new new 运算符创建< : strong> new 对象和调用 sub new - 构造函数 - 您的对象可以执行任何其他初始化。

需要清楚,dim(或private)仅声明一个变量及其type。该变量的范围 - 是为整个模块/类存在还是在过程中本地化的范围 - 由确定 被声明。 私人|朋友| public定义访问级别,而不是范围

有关更多信息,请参见:


数组

数组也必须进行实例化:

Private arr as String()

仅声明,而不是创建此数组。有几种初始化数组的方法:

Private arr as String() = New String(10){}
' or
Private arr() As String = New String(10){}

' For a local array (in a procedure) and using 'Option Infer':
Dim arr = New String(10) {}

注意:从VS 2010开始,当使用文字和选项初始化本地数组时,as&lt; type; type&gt; and <代码>新元素是可选的:

Dim myDbl As Double() = {1.5, 2, 9.9, 18, 3.14}
Dim myDbl = New Double() {1.5, 2, 9.9, 18, 3.14}
Dim myDbl() = {1.5, 2, 9.9, 18, 3.14}

从分配的数据中推断出数据类型和数组大小。类/模块级别的声明仍然需要as type&gt; option strict

Private myDoubles As Double() = {1.5, 2, 9.9, 18, 3.14}

示例:类对象的数组

Dim arrFoo(5) As Foo

For i As Integer = 0 To arrFoo.Count - 1
   arrFoo(i).Bar = i * 10       ' Exception
Next

已经创建了数组,但是foo对象没有。

补充

For i As Integer = 0 To arrFoo.Count - 1
    arrFoo(i) = New Foo()         ' Create Foo instance
    arrFoo(i).Bar = i * 10
Next

使用列表(t)将使没有有效对象的元素很难:

Dim FooList As New List(Of Foo)     ' List created, but it is empty
Dim f As Foo                        ' Temporary variable for the loop

For i As Integer = 0 To 5
    f = New Foo()                    ' Foo instance created
    f.Bar =  i * 10
    FooList.Add(f)                   ' Foo object added to list
Next

有关更多信息,请参见:


列表和集合

。还必须实例化或创建净收集(其中有许多品种 - 列表,字典等)。

Private myList As List(Of String)
..
myList.Add("ziggy")           ' NullReference

出于相同的原因,您会获得相同的例外 - myList仅声明,但没有创建实例。补救措施是相同的:

myList = New List(Of String)

' Or create an instance when declared:
Private myList As New List(Of String)

一个常见的监督是使用Collection type的类:

Public Class Foo
    Private barList As List(Of Bar)

    Friend Function BarCount As Integer
        Return barList.Count
    End Function

    Friend Sub AddItem(newBar As Bar)
        If barList.Contains(newBar) = False Then
            barList.Add(newBar)
        End If
    End Function

任何一个过程都会导致NRE,因为barlist仅声明,而不是实例化。创建foo的实例也不会创建内部barlist的实例。可能是在构造函数中执行此操作的目的:

Public Sub New         ' Constructor
    ' Stuff to do when a new Foo is created...
    barList = New List(Of Bar)
End Sub

和以前一样,这是不正确的:

Public Sub New()
    ' Creates another barList local to this procedure
     Dim barList As New List(Of Bar)
End Sub

有关更多信息,请参见 list(t) class


与数据库一起使用的数据提供商对象

为nullReference提供了许多机会,因为可能有许多对象(命令Connectiontrans> trassactiondataSetdataTabledatarows ....)一次使用。 注意:您正在使用哪个数据提供商 - MySQL,SQL Server,OLEDB等 - Concepts 是相同的。

示例1

Dim da As OleDbDataAdapter
Dim ds As DataSet
Dim MaxRows As Integer

con.Open()
Dim sql = "SELECT * FROM tblfoobar_List"
da = New OleDbDataAdapter(sql, con)
da.Fill(ds, "foobar")
con.Close()

MaxRows = ds.Tables("foobar").Rows.Count      ' Error

和以前一样,声明了ds数据集对象,但是从未创建实例。 dataAdapter将填充现有的数据集,而不是创建一个。在这种情况下,由于ds是局部变量,因此IDE警告您可能会发生:

​。不要忽略警告。

补救症

Dim ds As New DataSet

示例2

ds = New DataSet
da = New OleDBDataAdapter(sql, con)
da.Fill(ds, "Employees")

txtID.Text = ds.Tables("Employee").Rows(0).Item(1)
txtID.Name = ds.Tables("Employee").Rows(0).Item(2)

在这里错字是一个问题:员工 vs 雇员。没有DataTable命名为“员工”创建的,因此nullReferenceException尝试访问它的结果。另一个潜在的问题是假设将有项目,当SQL包含一个where子句时,可能并非如此。

补救症

由于使用一个表,使用表(0)将避免拼写错误。检查行。COUNT.COUNT也可以帮助:

If ds.Tables(0).Rows.Count > 0 Then
    txtID.Text = ds.Tables(0).Rows(0).Item(1)
    txtID.Name = ds.Tables(0).Rows(0).Item(2)
End If

fill是返回行的数量受影响的功能:

If da.Fill(ds, "Employees") > 0 Then...

示例3

Dim da As New OleDb.OleDbDataAdapter("SELECT TICKET.TICKET_NO,
        TICKET.CUSTOMER_ID, ... FROM TICKET_RESERVATION AS TICKET INNER JOIN
        FLIGHT_DETAILS AS FLIGHT ... WHERE [TICKET.TICKET_NO]= ...", con)
Dim ds As New DataSet
da.Fill(ds)

If ds.Tables("TICKET_RESERVATION").Rows.Count > 0 Then

dataAdapter将提供tableNames,如上一个示例所示,但不会从SQL或数据库表中解析名称。结果,ds.table(“ ticket_reservation”)引用不存在的表。

补救症是相同的,请参考索引:

If ds.Tables(0).Rows.Count > 0 Then

另请参见 DataTable类


对象路径/嵌套

If myFoo.Bar.Items IsNot Nothing Then
   ...

代码仅测试项目,而myfoobar也可能没有。 补救症是一次测试一个对象的整个链或路径:

If (myFoo IsNot Nothing) AndAlso
    (myFoo.Bar IsNot Nothing) AndAlso
    (myFoo.Bar.Items IsNot Nothing) Then
    ....

andoLSO很重要。一旦遇到第一个false条件,将不会执行后续测试。这允许代码一次安全地“钻入”一个“级别”,仅在(如果)myfoo之后评估myfoo.bar才能确定有效。编码复杂对象时,对象链或路径可能会变得很长:

myBase.myNodes(3).Layer.SubLayer.Foo.Files.Add("somefilename")

不可能引用null对象的任何“下游”的内容。这也适用于控件:

myWebBrowser.Document.GetElementById("formfld1").InnerText = "some value"

此处,mywebbrowserdocument可能不存在formfld1元素可能不存在。


UI控件

Dim cmd5 As New SqlCommand("select Cartons, Pieces, Foobar " _
     & "FROM Invoice where invoice_no = '" & _
     Me.ComboBox5.SelectedItem.ToString.Trim & "' And category = '" & _
     Me.ListBox1.SelectedItem.ToString.Trim & "' And item_name = '" & _
     Me.ComboBox2.SelectedValue.ToString.Trim & "' And expiry_date = '" & _
     Me.expiry.Text & "'", con)

除其他方面,此代码不会预期用户可能不会在一个或多个UI控件中选择某些内容。 ListBox1.SelectedItem很可能是nothing,因此listbox1.selectedItem.toString将导致NRE。

Resedy

在使用该数据之前验证数据(还使用strict和SQL参数):

Dim expiry As DateTime         ' for text date validation
If (ComboBox5.SelectedItems.Count > 0) AndAlso
    (ListBox1.SelectedItems.Count > 0) AndAlso
    (ComboBox2.SelectedItems.Count > 0) AndAlso
    (DateTime.TryParse(expiry.Text, expiry) Then

    '... do stuff
Else
    MessageBox.Show(...error message...)
End If

或者,您可以使用(combobox5.SelectedItem issonnot nothot nothot) /code>


Visual Basic表单

Public Class Form1

    Private NameBoxes = New TextBox(5) {Controls("TextBox1"), _
                   Controls("TextBox2"), Controls("TextBox3"), _
                   Controls("TextBox4"), Controls("TextBox5"), _
                   Controls("TextBox6")}

    ' same thing in a different format:
    Private boxList As New List(Of TextBox) From {TextBox1, TextBox2, TextBox3 ...}

    ' Immediate NRE:
    Private somevar As String = Me.Controls("TextBox1").Text

这是获得NRE的相当常见方法。在C#中,根据其编码方式,IDE将报告Controls在当前上下文中不存在,或“不能引用非静态成员”。因此,在某种程度上,这是仅VB的情况。它也很复杂,因为它会导致故障级联。

无法以这种方式初始化阵列和集合。此初始化代码将在之前运行 构造函数创建form> formControls 。结果:

  • 列表和集合将简单地为空。
  • 数组将包含
  • somevar分配的五个元素,因为没有什么都没有.Text 属性

引用数组元素以后会导致NRE。如果您在form_load中执行此操作,则由于奇数错误,IDE 可能不会在发生时报告异常。当您的代码试图使用数组时,此例外将弹出以后。这个“沉默异常”是在这篇文章中详细介绍。出于我们的目的,关键是,当创建表单时发生灾难性的事情(sub new表单加载事件)时,异常可能会毫无报告为只是显示表单。

由于您的sub newform load事件将在NRE之后运行,因此 可以使很多其他事情都可以不进行原始化。

Sub Form_Load(..._
   '...
   Dim name As String = NameBoxes(2).Text        ' NRE
   ' ...
   ' More code (which will likely not be executed)
   ' ...
End Sub

这适用于任何和所有控制和组件的参考文献,使这些参考是非法的

Public Class Form1

    Private myFiles() As String = Me.OpenFileDialog1.FileName & ...
    Private dbcon As String = OpenFileDialog1.FileName & ";Jet Oledb..."
    Private studentName As String = TextBox13.Text

注释

声明在形式级别上的容器,但是 当控件 do 存在时,在形式负载事件处理程序中它们。只要您的代码在oniratizecomponent调用:

' Module level declaration
Private NameBoxes as TextBox()
Private studentName As String

' Form Load, Form Shown or Sub New:
'
' Using the OP's approach (illegal using OPTION STRICT)
NameBoxes = New TextBox() {Me.Controls("TextBox1"), Me.Controls("TestBox2"), ...)
studentName = TextBox32.Text           ' For simple control references

数组代码可能还不属于树林之后,就可以在sub new中完成。在容器控件中的任何控件(例如groupbox面板)都不会在me.controls中找到;他们将在该面板或GroupBox的控件集合中。拼写控件名称时,也不会返回控件(“ TestBox2”)。在这种情况下,都将再次存储在这些数组元素中,并且在您尝试引用它时会产生NRE。

现在您知道您要寻找的东西,这些应该很容易找到:
“

“ button2”位于panel

补救措施 上

而不是使用表单的Controls集合而不是通过名称进行

' Declaration
Private NameBoxes As TextBox()

' Initialization -  simple and easy to read, hard to botch:
NameBoxes = New TextBox() {TextBox1, TextBox2, ...)

' Initialize a List
NamesList = New List(Of TextBox)({TextBox1, TextBox2, TextBox3...})
' or
NamesList = New List(Of TextBox)
NamesList.AddRange({TextBox1, TextBox2, TextBox3...})

间接

Private bars As New List(Of Bars)        ' Declared and created

Public Function BarList() As List(Of Bars)
    bars.Clear
    If someCondition Then
        For n As Integer = 0 to someValue
            bars.Add(GetBar(n))
        Next n
    Else
        Exit Function
    End If

    Return bars
End Function

参考值和nullReferenceException可能结果'。您可以通过退出功能返回来抑制警告,但这并不能解决问题。任何试图使用返回时somecondition = false的任何试图

bList = myFoo.BarList()
For Each b As Bar in bList      ' EXCEPTION
      ...

使用

返回Blist 。返回 list与返回nothing不同。如果返回的对象可以没有,请在使用之前进行测试:

 bList = myFoo.BarList()
 If bList IsNot Nothing Then...

实现/捕获不良实现的尝试

/捕获可能会隐藏问题的位置,并导致新的问题:

Dim dr As SqlDataReader
Try
    Dim lnk As LinkButton = TryCast(sender, LinkButton)
    Dim gr As GridViewRow = DirectCast(lnk.NamingContainer, GridViewRow)
    Dim eid As String = GridView1.DataKeys(gr.RowIndex).Value.ToString()
    ViewState("username") = eid
    sqlQry = "select FirstName, Surname, DepartmentName, ExtensionName, jobTitle,
             Pager, mailaddress, from employees1 where username='" & eid & "'"
    If connection.State <> ConnectionState.Open Then
        connection.Open()
    End If
    command = New SqlCommand(sqlQry, connection)

    'More code fooing and barring

    dr = command.ExecuteReader()
    If dr.Read() Then
        lblFirstName.Text = Convert.ToString(dr("FirstName"))
        ...
    End If
    mpe.Show()
Catch

Finally
    command.Dispose()
    dr.Close()             ' <-- NRE
    connection.Close()
End Try

这是未预期创建对象的情况,但也演示了空的catch的对抗有用性。

SQL中有一个额外的逗号(在“ Mailaddress”之后),在.executereader中导致例外。 catch什么都不做之后,最后试图进行清洁,但是由于您不能close> close null datareader object ,一个全新的nullReferenceException结果。

空的catch块是魔鬼的游乐场。这种操作让他感到困惑,为什么他在最终块中获得NRE。在其他情况下,一个空的catch可能会导致其他事情进一步出现在下游,并使您花时间在错误的位置查看错误的问题。 (上述上述的“沉默异常”提供了相同的娱乐价值。)

Remedy

不要使用空的尝试/捕获块 - 让代码崩溃,以便您可以a)确定原因b)确定位置c)应用适当的补救措施。尝试/捕获块并不是要隐藏异常的人,以解决这些人的唯一资格 - 开发人员。


dbnull与isdbnull函数不一样,

For Each row As DataGridViewRow In dgvPlanning.Rows
    If Not IsDBNull(row.Cells(0).Value) Then
        ...

用于测试如果a value equals system.dbnull的rel =“ noreferrer”>

system.dbnull值表示对象表示缺失或不存在数据。 dbnull与什么都不相同,这表明尚未初始化变量。

Remedy

If row.Cells(0) IsNot Nothing Then ...

与以前一样,您可以一无所获,然后对于特定值:

If (row.Cells(0) IsNot Nothing) AndAlso (IsDBNull(row.Cells(0).Value) = False) Then

示例2

Dim getFoo = (From f In dbContext.FooBars
               Where f.something = something
               Select f).FirstOrDefault

If Not IsDBNull(getFoo) Then
    If IsDBNull(getFoo.user_id) Then
        txtFirst.Text = getFoo.first_name
    Else
       ...

firstordEfault返回第一个项目或默认值,该值是参考类型的无,从不 dbnull :

If getFoo IsNot Nothing Then...

控制

Dim chk As CheckBox

chk = CType(Me.Controls(chkName), CheckBox)
If chk.Checked Then
    Return chk
End If

如果复选框带有chkname 找不到(或存在于groupbox)中,然后chk将一无所有,并试图引用任何属性会导致例外。

补救

If (chk IsNot Nothing) AndAlso (chk.Checked) Then ...

datagridView

dgv会定期看到一些怪癖:

dgvBooks.DataSource = loan.Books
dgvBooks.Columns("ISBN").Visible = True       ' NullReferenceException
dgvBooks.Columns("Title").DefaultCellStyle.Format = "C"
dgvBooks.Columns("Author").DefaultCellStyle.Format = "C"
dgvBooks.Columns("Price").DefaultCellStyle.Format = "C"

如果dgvbooks具有autogeneratecolumns = true,它将创建列,但不会命名它们,因此上述代码以名称引用时会失败。

Remedy

手动命名列,或通过索引参考:

dgvBooks.Columns(0).Visible = True

请当心newRow。

xlWorkSheet = xlWorkBook.Sheets("sheet1")

For i = 0 To myDGV.RowCount - 1
    For j = 0 To myDGV.ColumnCount - 1
        For k As Integer = 1 To myDGV.Columns.Count
            xlWorkSheet.Cells(1, k) = myDGV.Columns(k - 1).HeaderText
            xlWorkSheet.Cells(i + 2, j + 1) = myDGV(j, i).Value.ToString()
        Next
    Next
Next

示例2 -当您的dataGridView具有allowusertoAddrows at true true <时, /code>(默认值),底部的空白/新行中的单元格都包含nothere。大多数使用内容的尝试(例如,toString)将导致NRE。

补救症

使用for/enver循环并测试isNewrow属性属性来确定是否是最后一行。如果allow usertoAddrows是真的:

For Each r As DataGridViewRow in myDGV.Rows
    If r.IsNewRow = False Then
         ' ok to use this row

如果您确实使用循环,请修改行计数或使用 exit 时> isNewrow 是正确的。


在某些情况下,尝试使用my.settings的My.Settings(StringCollection)

,它是StringCollection可能在您第一次使用时会导致nullReference。解决方案是相同的,但不那么明显。考虑:

My.Settings.FooBars.Add("ziggy")         ' foobars is a string collection

由于VB正在为您管理设置,因此可以期望它初始化该集合是合理的。它会,但是只有以前您以前已经在集合中添加了初始条目(在“设置编辑器”中)。由于(显然)在添加项目时(显然是)初始化了该集合,因此当设置编辑器中没有项目要添加时,它仍然是nothing

Remedy

初始化表单load> LOAD事件处理程序中的设置集合,如果/在需要时:

If My.Settings.FooBars Is Nothing Then
    My.Settings.FooBars = New System.Collections.Specialized.StringCollection
End If

通常,settings Collection只需要初始化第一次运行应用程序。另一种补救措施是在 project -&gt中为您的收藏中添加初始价值;设置| Foobars ,保存项目,然后删除假值。


关键点

您可能忘记了操作员。

或者

您认为可以完美地执行以将初始化的对象返回您的代码。

不要忽略编译器警告(永远),并且使用选项严格在上(始终)。


msdn nullReference异常

NullReference Exception — Visual Basic

The NullReference Exception for Visual Basic is no different from the one in C#. After all, they are both reporting the same exception defined in the .NET Framework which they both use. Causes unique to Visual Basic are rare (perhaps only one).

This answer will use Visual Basic terms, syntax, and context. The examples used come from a large number of past Stack  Overflow questions. This is to maximize relevance by using the kinds of situations often seen in posts. A bit more explanation is also provided for those who might need it. An example similar to yours is very likely listed here.

Note:

  1. This is concept-based: there is no code for you to paste into your project. It is intended to help you understand what causes a NullReferenceException (NRE), how to find it, how to fix it, and how to avoid it. An NRE can be caused many ways so this is unlikely to be your sole encounter.
  2. The examples (from Stack  Overflow posts) do not always show the best way to do something in the first place.
  3. Typically, the simplest remedy is used.

Basic Meaning

The message "Object not set to an instance of Object" means you are trying to use an object which has not been initialized. This boils down to one of these:

  • Your code declared an object variable, but it did not initialize it (create an instance or 'instantiate' it)
  • Something which your code assumed would initialize an object, did not
  • Possibly, other code prematurely invalidated an object still in use

Finding The Cause

Since the problem is an object reference which is Nothing, the answer is to examine them to find out which one. Then determine why it is not initialized. Hold the mouse over the various variables and Visual Studio (VS) will show their values - the culprit will be Nothing.

IDE debug display

You should also remove any Try/Catch blocks from the relevant code, especially ones where there is nothing in the Catch block. This will cause your code to crash when it tries to use an object which is Nothing. This is what you want because it will identify the exact location of the problem, and allow you to identify the object causing it.

A MsgBox in the Catch which displays Error while... will be of little help. This method also leads to very bad Stack  Overflow questions, because you can't describe the actual exception, the object involved or even the line of code where it happens.

You can also use the Locals Window (Debug -> Windows -> Locals) to examine your objects.

Once you know what and where the problem is, it is usually fairly easy to fix and faster than posting a new question.

See also:

Examples and Remedies

Class Objects / Creating an Instance

Dim reg As CashRegister
...
TextBox1.Text = reg.Amount         ' NRE

The problem is that Dim does not create a CashRegister object; it only declares a variable named reg of that Type. Declaring an object variable and creating an instance are two different things.

Remedy

The New operator can often be used to create the instance when you declare it:

Dim reg As New CashRegister        ' [New] creates instance, invokes the constructor

' Longer, more explicit form:
Dim reg As CashRegister = New CashRegister

When it is only appropriate to create the instance later:

Private reg As CashRegister         ' Declare
  ...
reg = New CashRegister()            ' Create instance

Note: Do not use Dim again in a procedure, including the constructor (Sub New):

Private reg As CashRegister
'...

Public Sub New()
   '...
   Dim reg As New CashRegister
End Sub

This will create a local variable, reg, which exists only in that context (sub). The reg variable with module level Scope which you will use everywhere else remains Nothing.

Missing the New operator is the #1 cause of NullReference Exceptions seen in the Stack  Overflow questions reviewed.

Visual Basic tries to make the process clear repeatedly using New: Using the New Operator creates a new object and calls Sub New -- the constructor -- where your object can perform any other initialization.

To be clear, Dim (or Private) only declares a variable and its Type. The Scope of the variable - whether it exists for the entire module/class or is local to a procedure - is determined by where it is declared. Private | Friend | Public defines the access level, not Scope.

For more information, see:


Arrays

Arrays must also be instantiated:

Private arr as String()

This array has only been declared, not created. There are several ways to initialize an array:

Private arr as String() = New String(10){}
' or
Private arr() As String = New String(10){}

' For a local array (in a procedure) and using 'Option Infer':
Dim arr = New String(10) {}

Note: Beginning with VS 2010, when initializing a local array using a literal and Option Infer, the As <Type> and New elements are optional:

Dim myDbl As Double() = {1.5, 2, 9.9, 18, 3.14}
Dim myDbl = New Double() {1.5, 2, 9.9, 18, 3.14}
Dim myDbl() = {1.5, 2, 9.9, 18, 3.14}

The data Type and array size are inferred from the data being assigned. Class/Module level declarations still require As <Type> with Option Strict:

Private myDoubles As Double() = {1.5, 2, 9.9, 18, 3.14}

Example: Array of class objects

Dim arrFoo(5) As Foo

For i As Integer = 0 To arrFoo.Count - 1
   arrFoo(i).Bar = i * 10       ' Exception
Next

The array has been created, but the Foo objects in it have not.

Remedy

For i As Integer = 0 To arrFoo.Count - 1
    arrFoo(i) = New Foo()         ' Create Foo instance
    arrFoo(i).Bar = i * 10
Next

Using a List(Of T) will make it quite difficult to have an element without a valid object:

Dim FooList As New List(Of Foo)     ' List created, but it is empty
Dim f As Foo                        ' Temporary variable for the loop

For i As Integer = 0 To 5
    f = New Foo()                    ' Foo instance created
    f.Bar =  i * 10
    FooList.Add(f)                   ' Foo object added to list
Next

For more information, see:


Lists and Collections

.NET collections (of which there are many varieties - Lists, Dictionary, etc.) must also be instantiated or created.

Private myList As List(Of String)
..
myList.Add("ziggy")           ' NullReference

You get the same exception for the same reason - myList was only declared, but no instance created. The remedy is the same:

myList = New List(Of String)

' Or create an instance when declared:
Private myList As New List(Of String)

A common oversight is a class which uses a collection Type:

Public Class Foo
    Private barList As List(Of Bar)

    Friend Function BarCount As Integer
        Return barList.Count
    End Function

    Friend Sub AddItem(newBar As Bar)
        If barList.Contains(newBar) = False Then
            barList.Add(newBar)
        End If
    End Function

Either procedure will result in an NRE, because barList is only declared, not instantiated. Creating an instance of Foo will not also create an instance of the internal barList. It may have been the intent to do this in the constructor:

Public Sub New         ' Constructor
    ' Stuff to do when a new Foo is created...
    barList = New List(Of Bar)
End Sub

As before, this is incorrect:

Public Sub New()
    ' Creates another barList local to this procedure
     Dim barList As New List(Of Bar)
End Sub

For more information, see List(Of T) Class.


Data Provider Objects

Working with databases presents many opportunities for a NullReference because there can be many objects (Command, Connection, Transaction, Dataset, DataTable, DataRows....) in use at once. Note: It does not matter which data provider you are using -- MySQL, SQL Server, OleDB, etc. -- the concepts are the same.

Example 1

Dim da As OleDbDataAdapter
Dim ds As DataSet
Dim MaxRows As Integer

con.Open()
Dim sql = "SELECT * FROM tblfoobar_List"
da = New OleDbDataAdapter(sql, con)
da.Fill(ds, "foobar")
con.Close()

MaxRows = ds.Tables("foobar").Rows.Count      ' Error

As before, the ds Dataset object was declared, but an instance was never created. The DataAdapter will fill an existing DataSet, not create one. In this case, since ds is a local variable, the IDE warns you that this might happen:

img

When declared as a module/class level variable, as appears to be the case with con, the compiler can't know if the object was created by an upstream procedure. Do not ignore warnings.

Remedy

Dim ds As New DataSet

Example 2

ds = New DataSet
da = New OleDBDataAdapter(sql, con)
da.Fill(ds, "Employees")

txtID.Text = ds.Tables("Employee").Rows(0).Item(1)
txtID.Name = ds.Tables("Employee").Rows(0).Item(2)

A typo is a problem here: Employees vs Employee. There was no DataTable named "Employee" created, so a NullReferenceException results trying to access it. Another potential problem is assuming there will be Items which may not be so when the SQL includes a WHERE clause.

Remedy

Since this uses one table, using Tables(0) will avoid spelling errors. Examining Rows.Count can also help:

If ds.Tables(0).Rows.Count > 0 Then
    txtID.Text = ds.Tables(0).Rows(0).Item(1)
    txtID.Name = ds.Tables(0).Rows(0).Item(2)
End If

Fill is a function returning the number of Rows affected which can also be tested:

If da.Fill(ds, "Employees") > 0 Then...

Example 3

Dim da As New OleDb.OleDbDataAdapter("SELECT TICKET.TICKET_NO,
        TICKET.CUSTOMER_ID, ... FROM TICKET_RESERVATION AS TICKET INNER JOIN
        FLIGHT_DETAILS AS FLIGHT ... WHERE [TICKET.TICKET_NO]= ...", con)
Dim ds As New DataSet
da.Fill(ds)

If ds.Tables("TICKET_RESERVATION").Rows.Count > 0 Then

The DataAdapter will provide TableNames as shown in the previous example, but it does not parse names from the SQL or database table. As a result, ds.Tables("TICKET_RESERVATION") references a non-existent table.

The Remedy is the same, reference the table by index:

If ds.Tables(0).Rows.Count > 0 Then

See also DataTable Class.


Object Paths / Nested

If myFoo.Bar.Items IsNot Nothing Then
   ...

The code is only testing Items while both myFoo and Bar may also be Nothing. The remedy is to test the entire chain or path of objects one at a time:

If (myFoo IsNot Nothing) AndAlso
    (myFoo.Bar IsNot Nothing) AndAlso
    (myFoo.Bar.Items IsNot Nothing) Then
    ....

AndAlso is important. Subsequent tests will not be performed once the first False condition is encountered. This allows the code to safely 'drill' into the object(s) one 'level' at a time, evaluating myFoo.Bar only after (and if) myFoo is determined to be valid. Object chains or paths can get quite long when coding complex objects:

myBase.myNodes(3).Layer.SubLayer.Foo.Files.Add("somefilename")

It is not possible to reference anything 'downstream' of a null object. This also applies to controls:

myWebBrowser.Document.GetElementById("formfld1").InnerText = "some value"

Here, myWebBrowser or Document could be Nothing or the formfld1 element may not exist.


UI Controls

Dim cmd5 As New SqlCommand("select Cartons, Pieces, Foobar " _
     & "FROM Invoice where invoice_no = '" & _
     Me.ComboBox5.SelectedItem.ToString.Trim & "' And category = '" & _
     Me.ListBox1.SelectedItem.ToString.Trim & "' And item_name = '" & _
     Me.ComboBox2.SelectedValue.ToString.Trim & "' And expiry_date = '" & _
     Me.expiry.Text & "'", con)

Among other things, this code does not anticipate that the user may not have selected something in one or more UI controls. ListBox1.SelectedItem may well be Nothing, so ListBox1.SelectedItem.ToString will result in an NRE.

Remedy

Validate data before using it (also use Option Strict and SQL parameters):

Dim expiry As DateTime         ' for text date validation
If (ComboBox5.SelectedItems.Count > 0) AndAlso
    (ListBox1.SelectedItems.Count > 0) AndAlso
    (ComboBox2.SelectedItems.Count > 0) AndAlso
    (DateTime.TryParse(expiry.Text, expiry) Then

    '... do stuff
Else
    MessageBox.Show(...error message...)
End If

Alternatively, you can use (ComboBox5.SelectedItem IsNot Nothing) AndAlso...


Visual Basic Forms

Public Class Form1

    Private NameBoxes = New TextBox(5) {Controls("TextBox1"), _
                   Controls("TextBox2"), Controls("TextBox3"), _
                   Controls("TextBox4"), Controls("TextBox5"), _
                   Controls("TextBox6")}

    ' same thing in a different format:
    Private boxList As New List(Of TextBox) From {TextBox1, TextBox2, TextBox3 ...}

    ' Immediate NRE:
    Private somevar As String = Me.Controls("TextBox1").Text

This is a fairly common way to get an NRE. In C#, depending on how it is coded, the IDE will report that Controls does not exist in the current context, or "cannot reference non-static member". So, to some extent, this is a VB-only situation. It is also complex because it can result in a failure cascade.

The arrays and collections cannot be initialized this way. This initialization code will run before the constructor creates the Form or the Controls. As a result:

  • Lists and Collection will simply be empty
  • The Array will contain five elements of Nothing
  • The somevar assignment will result in an immediate NRE because Nothing doesn't have a .Text property

Referencing array elements later will result in an NRE. If you do this in Form_Load, due to an odd bug, the IDE may not report the exception when it happens. The exception will pop up later when your code tries to use the array. This "silent exception" is detailed in this post. For our purposes, the key is that when something catastrophic happens while creating a form (Sub New or Form Load event), exceptions may go unreported, the code exits the procedure and just displays the form.

Since no other code in your Sub New or Form Load event will run after the NRE, a great many other things can be left uninitialized.

Sub Form_Load(..._
   '...
   Dim name As String = NameBoxes(2).Text        ' NRE
   ' ...
   ' More code (which will likely not be executed)
   ' ...
End Sub

Note this applies to any and all control and component references making these illegal where they are:

Public Class Form1

    Private myFiles() As String = Me.OpenFileDialog1.FileName & ...
    Private dbcon As String = OpenFileDialog1.FileName & ";Jet Oledb..."
    Private studentName As String = TextBox13.Text

Partial Remedy

It is curious that VB does not provide a warning, but the remedy is to declare the containers at the form level, but initialize them in form load event handler when the controls do exist. This can be done in Sub New as long as your code is after the InitializeComponent call:

' Module level declaration
Private NameBoxes as TextBox()
Private studentName As String

' Form Load, Form Shown or Sub New:
'
' Using the OP's approach (illegal using OPTION STRICT)
NameBoxes = New TextBox() {Me.Controls("TextBox1"), Me.Controls("TestBox2"), ...)
studentName = TextBox32.Text           ' For simple control references

The array code may not be out of the woods yet. Any controls which are in a container control (like a GroupBox or Panel) will not be found in Me.Controls; they will be in the Controls collection of that Panel or GroupBox. Nor will a control be returned when the control name is misspelled ("TeStBox2"). In such cases, Nothing will again be stored in those array elements and an NRE will result when you attempt to reference it.

These should be easy to find now that you know what you are looking for:
VS shows you the error of your ways

"Button2" resides on a Panel

Remedy

Rather than indirect references by name using the form's Controls collection, use the control reference:

' Declaration
Private NameBoxes As TextBox()

' Initialization -  simple and easy to read, hard to botch:
NameBoxes = New TextBox() {TextBox1, TextBox2, ...)

' Initialize a List
NamesList = New List(Of TextBox)({TextBox1, TextBox2, TextBox3...})
' or
NamesList = New List(Of TextBox)
NamesList.AddRange({TextBox1, TextBox2, TextBox3...})

Function Returning Nothing

Private bars As New List(Of Bars)        ' Declared and created

Public Function BarList() As List(Of Bars)
    bars.Clear
    If someCondition Then
        For n As Integer = 0 to someValue
            bars.Add(GetBar(n))
        Next n
    Else
        Exit Function
    End If

    Return bars
End Function

This is a case where the IDE will warn you that 'not all paths return a value and a NullReferenceException may result'. You can suppress the warning, by replacing Exit Function with Return Nothing, but that does not solve the problem. Anything which tries to use the return when someCondition = False will result in an NRE:

bList = myFoo.BarList()
For Each b As Bar in bList      ' EXCEPTION
      ...

Remedy

Replace Exit Function in the function with Return bList. Returning an empty List is not the same as returning Nothing. If there is a chance that a returned object can be Nothing, test before using it:

 bList = myFoo.BarList()
 If bList IsNot Nothing Then...

Poorly Implemented Try/Catch

A badly implemented Try/Catch can hide where the problem is and result in new ones:

Dim dr As SqlDataReader
Try
    Dim lnk As LinkButton = TryCast(sender, LinkButton)
    Dim gr As GridViewRow = DirectCast(lnk.NamingContainer, GridViewRow)
    Dim eid As String = GridView1.DataKeys(gr.RowIndex).Value.ToString()
    ViewState("username") = eid
    sqlQry = "select FirstName, Surname, DepartmentName, ExtensionName, jobTitle,
             Pager, mailaddress, from employees1 where username='" & eid & "'"
    If connection.State <> ConnectionState.Open Then
        connection.Open()
    End If
    command = New SqlCommand(sqlQry, connection)

    'More code fooing and barring

    dr = command.ExecuteReader()
    If dr.Read() Then
        lblFirstName.Text = Convert.ToString(dr("FirstName"))
        ...
    End If
    mpe.Show()
Catch

Finally
    command.Dispose()
    dr.Close()             ' <-- NRE
    connection.Close()
End Try

This is a case of an object not being created as expected, but also demonstrates the counter usefulness of an empty Catch.

There is an extra comma in the SQL (after 'mailaddress') which results in an exception at .ExecuteReader. After the Catch does nothing, Finally tries to perform clean up, but since you cannot Close a null DataReader object, a brand new NullReferenceException results.

An empty Catch block is the devil's playground. This OP was baffled why he was getting an NRE in the Finally block. In other situations, an empty Catch may result in something else much further downstream going haywire and cause you to spend time looking at the wrong things in the wrong place for the problem. (The "silent exception" described above provides the same entertainment value.)

Remedy

Don't use empty Try/Catch blocks - let the code crash so you can a) identify the cause b) identify the location and c) apply a proper remedy. Try/Catch blocks are not intended to hide exceptions from the person uniquely qualified to fix them - the developer.


DBNull is not the same as Nothing

For Each row As DataGridViewRow In dgvPlanning.Rows
    If Not IsDBNull(row.Cells(0).Value) Then
        ...

The IsDBNull function is used to test if a value equals System.DBNull: From MSDN:

The System.DBNull value indicates that the Object represents missing or non-existent data. DBNull is not the same as Nothing, which indicates that a variable has not yet been initialized.

Remedy

If row.Cells(0) IsNot Nothing Then ...

As before, you can test for Nothing, then for a specific value:

If (row.Cells(0) IsNot Nothing) AndAlso (IsDBNull(row.Cells(0).Value) = False) Then

Example 2

Dim getFoo = (From f In dbContext.FooBars
               Where f.something = something
               Select f).FirstOrDefault

If Not IsDBNull(getFoo) Then
    If IsDBNull(getFoo.user_id) Then
        txtFirst.Text = getFoo.first_name
    Else
       ...

FirstOrDefault returns the first item or the default value, which is Nothing for reference types and never DBNull:

If getFoo IsNot Nothing Then...

Controls

Dim chk As CheckBox

chk = CType(Me.Controls(chkName), CheckBox)
If chk.Checked Then
    Return chk
End If

If a CheckBox with chkName can't be found (or exists in a GroupBox), then chk will be Nothing and be attempting to reference any property will result in an exception.

Remedy

If (chk IsNot Nothing) AndAlso (chk.Checked) Then ...

The DataGridView

The DGV has a few quirks seen periodically:

dgvBooks.DataSource = loan.Books
dgvBooks.Columns("ISBN").Visible = True       ' NullReferenceException
dgvBooks.Columns("Title").DefaultCellStyle.Format = "C"
dgvBooks.Columns("Author").DefaultCellStyle.Format = "C"
dgvBooks.Columns("Price").DefaultCellStyle.Format = "C"

If dgvBooks has AutoGenerateColumns = True, it will create the columns, but it does not name them, so the above code fails when it references them by name.

Remedy

Name the columns manually, or reference by index:

dgvBooks.Columns(0).Visible = True

Example 2 — Beware of the NewRow

xlWorkSheet = xlWorkBook.Sheets("sheet1")

For i = 0 To myDGV.RowCount - 1
    For j = 0 To myDGV.ColumnCount - 1
        For k As Integer = 1 To myDGV.Columns.Count
            xlWorkSheet.Cells(1, k) = myDGV.Columns(k - 1).HeaderText
            xlWorkSheet.Cells(i + 2, j + 1) = myDGV(j, i).Value.ToString()
        Next
    Next
Next

When your DataGridView has AllowUserToAddRows as True (the default), the Cells in the blank/new row at the bottom will all contain Nothing. Most attempts to use the contents (for example, ToString) will result in an NRE.

Remedy

Use a For/Each loop and test the IsNewRow property to determine if it is that last row. This works whether AllowUserToAddRows is true or not:

For Each r As DataGridViewRow in myDGV.Rows
    If r.IsNewRow = False Then
         ' ok to use this row

If you do use a For n loop, modify the row count or use Exit For when IsNewRow is true.


My.Settings (StringCollection)

Under certain circumstances, trying to use an item from My.Settings which is a StringCollection can result in a NullReference the first time you use it. The solution is the same, but not as obvious. Consider:

My.Settings.FooBars.Add("ziggy")         ' foobars is a string collection

Since VB is managing Settings for you, it is reasonable to expect it to initialize the collection. It will, but only if you have previously added an initial entry to the collection (in the Settings editor). Since the collection is (apparently) initialized when an item is added, it remains Nothing when there are no items in the Settings editor to add.

Remedy

Initialize the settings collection in the form's Load event handler, if/when needed:

If My.Settings.FooBars Is Nothing Then
    My.Settings.FooBars = New System.Collections.Specialized.StringCollection
End If

Typically, the Settings collection will only need to be initialized the first time the application runs. An alternate remedy is to add an initial value to your collection in Project -> Settings | FooBars, save the project, then remove the fake value.


Key Points

You probably forgot the New operator.

or

Something you assumed would perform flawlessly to return an initialized object to your code, did not.

Don't ignore compiler warnings (ever) and use Option Strict On (always).


MSDN NullReference Exception

∞梦里开花 2025-01-25 19:05:00

另一种情况是当您将 null 对象转换为 值类型。例如,下面的代码:

object o = null;
DateTime d = (DateTime)o;

它将在强制转换时抛出 NullReferenceException。在上面的示例中这似乎很明显,但这可能发生在更“后期绑定”的复杂场景中,其中空对象已从您不拥有的某些代码返回,并且强制转换例如由某些自动系统生成。

其中一个示例是这个简单的 ASP.NET 与 Calendar 控件的绑定片段:

<asp:Calendar runat="server" SelectedDate="<%#Bind("Something")%>" />

这里,SelectedDate 实际上是 Calendar 的一个 DateTime 类型的属性 Web Control 类型,并且绑定可以完美地返回 null。隐式 ASP.NET 生成器将创建一段与上面的强制转换代码等效的代码。这将引发一个很难发现的 NullReferenceException ,因为它位于 ASP.NET 生成的代码中,可以正常编译......

Another scenario is when you cast a null object into a value type. For example, the code below:

object o = null;
DateTime d = (DateTime)o;

It will throw a NullReferenceException on the cast. It seems quite obvious in the above sample, but this can happen in more "late-binding" intricate scenarios where the null object has been returned from some code you don't own, and the cast is for example generated by some automatic system.

One example of this is this simple ASP.NET binding fragment with the Calendar control:

<asp:Calendar runat="server" SelectedDate="<%#Bind("Something")%>" />

Here, SelectedDate is in fact a property - of DateTime type - of the Calendar Web Control type, and the binding could perfectly return something null. The implicit ASP.NET Generator will create a piece of code that will be equivalent to the cast code above. And this will raise a NullReferenceException that is quite difficult to spot, because it lies in ASP.NET generated code which compiles fine...

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文