Here is a pull request which should resolve the issue with the latest version of Visual Studio and nullable types.
Basically I am dropping any calls to ValueOrDefault.
Where I find an expression which needs to access a nullable type I am substituting in an appropriate expression which accesses the Value or returns the default value. This way I am removing all calls to ValueOrDefault which is not supported in Linq to Entities.
I have run the changes through the entire test harness and all tests passed successfully.
Here is a pull request which should resolve the issue with the latest version of Visual Studio and nullable types.
Basically I am dropping any calls to ValueOrDefault. Where I find an expression which needs to access a nullable type I am substituting in an appropriate expression which accesses the Value or returns the default value. This way I am removing all calls to ValueOrDefault which is not supported in Linq to Entities.
I have run the changes through the entire test harness and all tests passed successfully.