"Not ... Is Nothing" versus "... IsNot Nothing"

vb.net nothing
nnnn picture nnnn · Sep 20, 2013 · Viewed 89.7k times · Source

Does anyone here use VB.NET and have a strong preference for or against using Not foo Is Nothing as opposed to foo IsNot Nothing? If so, why?

For Example

If var1 IsNot Nothing Then
...
End If

and

If Not var1 Is Nothing Then
...
End If

I just want to know which one is better?
Are they both equally acceptable?

Answer

Paul Michaels picture Paul Michaels · Sep 20, 2013

The 

If Not var1 Is Nothing Then

Is a hangover from VB6. There didn't used to be an IsNot, and so this was the only way to determine if a variable was not Nothing. It seems to be redundant in VB.NET.

Related questions

IsNothing versus Is Nothing

Does anyone here use VB.NET and have a strong preference for or against using IsNothing as opposed to Is Nothing (for example, If IsNothing(anObject) or If anObject Is Nothing...)? If so, why? EDIT: If you think they're both …

Read More
Why can't I check if a 'DateTime' is 'Nothing'?

In VB.NET, is there a way to set a DateTime variable to "not set"? And why is it possible to set a DateTime to Nothing, but not possible to check if it is Nothing? For example: Dim d As …

Read More
Nothing = String.Empty (Why are these equal?)

Why does the first if statement evaluate to true? I know if I use "is" instead of "=" then it won't evaluate to true. If I replace String.Empty with "Foo" it doesn't evaluate to true. Both String.Empty and "Foo" …

Read More