The exception is thrown on each query execution as a first chance exception for any provider that doesn't support spatial. It was [reported by a customer](http://blogs.msdn.com/b/adonet/archive/2013/05/30/ef6-beta-1-available.aspx?wa=wsignin1.0&CommentPosted=true#10423418) as being very annoying for debugging.
Throwing an exception in each query seems to be unnecessary waste and the contract of the method seems weird anyway. It seems that returning null is a better approach.
Note that strictly speaking this would be a breaking change but we are by far the main consumer of this provider API so in practice it should not affect anyone else.
Comments: This would in effect also take care of [workitem 1113](https://entityframework.codeplex.com/workitem/1113).
Throwing an exception in each query seems to be unnecessary waste and the contract of the method seems weird anyway. It seems that returning null is a better approach.
Note that strictly speaking this would be a breaking change but we are by far the main consumer of this provider API so in practice it should not affect anyone else.
Comments: This would in effect also take care of [workitem 1113](https://entityframework.codeplex.com/workitem/1113).