Tim Atkinson

I have looked further into this and can confirm that this can be resolved by adding a "return null;" at line 35 after the Console.WriteLine command within the catch.