Hi Roger,
Yes, they are opposites. We decided to change the name (and invert it) when we started exposing it in the public surface of DbContext in EF6. The broader meaning of the name in the DbContext API is also by-design. The first feature we added that is controlled by the flag is the expansion of comparisons to compensate for three-valued logic, but when we were deciding on the name we identified a few more ideas that we would like the flag to control in the future.
And yes, !_funcletizer.RootContext.ContextOptions.UseCSharpNullComparisonBehavior seems to be the easiest way to access the property. In fact we already use it in the ExpressionConverter that way.
Hope this helps,
Diego
Yes, they are opposites. We decided to change the name (and invert it) when we started exposing it in the public surface of DbContext in EF6. The broader meaning of the name in the DbContext API is also by-design. The first feature we added that is controlled by the flag is the expansion of comparisons to compensate for three-valued logic, but when we were deciding on the name we identified a few more ideas that we would like the flag to control in the future.
And yes, !_funcletizer.RootContext.ContextOptions.UseCSharpNullComparisonBehavior seems to be the easiest way to access the property. In fact we already use it in the ExpressionConverter that way.
Hope this helps,
Diego