I'm working with some VB.net projects and I decided to turn on Option Strict. It threw an error for this line:
If someProp Is Nothing OrElse String.IsNullOrEmpty(someProp.Value OrElse someProp.Value = "0") Then
This is what was intended:
If someProp Is Nothing OrElse String.IsNullOrEmpty(someProp.Value) OrElse someProp.Value = "0" Then
for option explicit! for the fact that I have several projects to go and I'm working in the order of best code to worst code.
The fact that VB.Net even considers this valid code is just batcrap insane.
This post has been edited by LetMeFinclOut: 10 February 2012 - 03:45 PM