ReSharper: how to remove “Possible 'System.Nul

问题:

Here is a piece of code:

        IUser user = managerUser.GetUserById(UserId);
        if ( user==null ) 
            throw new Exception(...);

        Quote quote = new Quote(user.FullName, user.Email);

Everything is fine here. But if I replace "if" line with the following one:

        ComponentException<MyUserManagerException>.FailIfTrue(user == null, "Can't find user with Id=" + UserId);

where function implementation is following:

public abstract class ComponentException<T> : ComponentException
        where T : ComponentException, new()
{
    public static void FailIfTrue(bool expression, string message)
    {
        if (expression)
        {
            T t = new T();
            t.SetErrorMessage(message);
            throw t;
        }
    }
    ...
}

Then resharper generates me a warning: Possible 'System.NullReferenceException' pointing on 1st usage of 'user' object.

Q1. Why it generates such exception? As far as I see if 'user==null' then exception will be generated and execution will never reach the usage point.

Q2. How to remove that warning? Please note: 1. I don't want to suppress this warning with comments (I will have a lot of similar pieces and don't want to transform my source code in 'commented garbase); 2. I don't want to changes resharper settings to change this problem from warning to 'suggestion' of 'hint'.

Thanks.

Any thoughts are welcome!

P.S. I am using resharper 5.1, MVSV 2008, C#

回答1:

Q1: Because Resharper doesn't do path analysing. It just sees a possible null reference and flags that.

Q2: You can't without doing either of what you provided already.

回答2:

Resharper only looks at the current method for its analysis, and does not recursively analyse other methods you call.

You can however direct Resharper a bit and give it meta-information about certain methods. It knows for example about "Assert.IsNotNull(a)", and will take that information into account for the analysis. It is possible to make an external annotations file for Resharper and give it extra information about a certain library to make its analysis better. Maybe this might offer a way to solve your problem.

More information can be found here.

An example showing how it's used for the library Microsoft.Contracts can be found here.

回答3:

A new answer in old post...

Here a little sample of my code regarding how to use CodeContract via ContractAnnotation with Resharper:

    [ContractAnnotation("value:null=>true")]
    public static bool IsNullOrEmpty(this string value)
    {
        return string.IsNullOrEmpty(value);
    }

It is very simple...if u find the breadcrumb in the wood. You can check other cases too.

Have a nice day

回答4:

You do know (or expect) that this code will throw an exception if there is a null reference:

ComponentException<MyUserManagerException>.FailIfTrue([...]);

However, since there is no contract specifying this, ReSharper has to assume that this is just a normal method call which may return without throwing any exception in any case.

Make this method implement the ReSharper contract, or as a simple workaround (which only affects debug mode, therefore no performance penalty for release mode), just after the FailIfTrue call:

Debug.Assert(user != null);

That will get rid of the warning, and as an added bonus do a runtime check in debug mode to ensure that the condition assumed by you after calling FailIfTrue is indeed met.

回答5:

This is caused by the Resharper engine. These "possible NullReferenceException" happen because someone (probably at Resharper) has declared/configured somewhere an annotation on the method.

Here is how it works: ReSharper NullReferenceException Analysis and Its Contracts

Unfortunately, sometimes, these useful annotation are just wrong.

When you detect an error, you should report it to JetBrains and they will update the annotations on the next release. They're used to this.

Meanwhile, you can try to fix it by yourself. Read the article for more :)

回答6:

Please check if you have any user==null if check above the given code. If there is, then ReSharper thinks that the variable "can be null" so recommends you to use a check/assert before referencing it. In some cases, that's the only way ReSharper can guess whether a variable can or cannot be null.