If you've been using linq to sql then you may have come across this baffling error before:
[VerificationException: Operation could destabilize the runtime.]
It would be a little nicer if the error message explained what operation could destablize the runtime and why, but alas, it does not.
So, what's causing the problem?
At least in some instances, this error will pop up because your entity class has a readonly field being used for storage. When linq to sql attempts to set a value on that field, it can't, so that error is thrown. If you want to be technical about it, you can set a readonly field's value through reflection, but it's bad practice. It's a good thing linq to sql doesn't do that, but the error it throws could be far more helpful.