One of our test fails migrating to DO5, we have a null type info in one case. I don't have code to reproduce it however you might have an idea of what's happening :
![alt text] ![alt text]
: http://support.x-tensive.com/upfiles/VS2012 DO4.png
: http://support.x-tensive.com/upfiles/vs2012 DO5.png
asked Sep 16 '16 at 04:32
Key.ResolveTypeInfo() method was introduced in 5.0.x. The code which was in Key.TypeInfo in 4.6.x moved to that method. Key.TypeInfo of 5.0.x will return null if Key.TypeReference.Accuracy is not TypeReferenceAccuracy.ExactType.
answered Sep 20 '16 at 03:54