Bottom line is, "Big picture" you should know if your instance is null before you proceed coding against it. there really is no reason to find a shortcut around that step.
That said, if you are using C# 3 or better you have Extensions methods which can be used to "hide" this detail from the main logic of your code. See below the sample with 'SomeType' and 'SomeMethod' and then an extension method called 'SomeMethodSafe'. You can call 'SomeMethodSafe' on a Null reference without error.
Don't try this at home.
namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{
SomeType s = null;
//s = new SomeType();
// uncomment me to try it with an instance
s.SomeMethodSafe();
Console.WriteLine("Done");
Console.ReadLine();
}
}
public class SomeType
{
public void SomeMethod()
{
Console.WriteLine("Success!");
}
}
public static class SampleExtensions
{
public static void SomeMethodSafe(this SomeType t)
{
if (t != null)
{
t.SomeMethod();
}
}
}
}