>>>>The way around this is to create a second model that has only the fields you want to update. In fact, that's probably best practice as you only query the data you really need.
>>>>
>>>
>>>Is it the only way? Say, I still want to be able to change ModifiedOn, ModifiedBy if I am editing and the first two if I am inserting.
>>>
>>>In other words, I may want to set ReadOnly attribute but conditionally.
>>
>>You could leave the EF model as is but create additional MVC models. More work though since you'd have to update the EF model from the MVC model in code....
>
>I have one MVC model which I use in both Edit and Add dialog which is the same view in my case. I don't know if I can still use the same view but different models depending on the Add vs. Edit - that may be an alternative solution.
>
>Also, the EF model is a property of my MVC model, e.g. I have Client Client property of MVC model.
>

In those scenarios I usually create 2 views, one for the one case, one for the other along with separate controller methods/actions (unless these are incredibly similar, then I may just handle it in the view and in the controller action). That usually means I also need a separate view model for each of them, each with their own attributes - I end up with 3 classes - one "common" view model class which contains all of the fields/attributes that are common to the other 2 (and that the other 2 will inherit from).