Aug 11, 2018 03:05 PM|PatriceSc|LINK
EF could still use the original value. You need to force that programmatically or you just want to see what happens when needed ?
My first thought would be to just run a SQL update to create a "true" concurrency error. Here you are trying to "simulate" a concurrency error by changing the client side value but it may or may not have the same effect.
Edit: missed you were trying to investigate a previous error. You checked on the database side that this column is really defined as a "rowversion" ? Do a SQL UPDATE and see if this column value is updated as well.