Option 1: Could you please put in a new dialogue that when you map a view that asks you which property should be the PK?...and not let you map it w/out setting it...and\or generate a compile error?
Option 2: Make the error message not be "Invalid object name 'voa_keygen'.", make it say "Entity X needs to have a primary key"
Reason I say that is I just got this
nice friendly guy again and the error is so obscure you don't really know why you're getting it. I mapped the View in last night before I left, and I got the error this morning so I had to go back through my steps on what I changed yesterday.
I guess what I'm saying is that this WILL cause the model to fail, you wont be able to use the model (not just the class), so put up a roadblock for us so we're not spinning our wheels trying to figure out what happened :) Don't let us get to that point.