I'm developing a Web API Service (in Visual Studio 2013), and I've added, in my solution, ADO.NET Entity Data Model (Database First).
All the tables I've included, are correctly created in my edmx diagram.
Then I've made some changes: I've added two new columns in the source database, and I've removed one column. So, when I try to update model from database the two new columns are added, while the removed column is still in my model and the message:
Error 11009: Property 'Image' is not mapped.
Image is the name of the removed column in the database.
Can I manually remove this property from model? Or is there another cleaner and safer way to do this?
Sure, as others says, changing the the approach could be a better way to work with EF and DB, but starting from the fact you need Database First, I think working with Database First Model has it's advantages, one of those (and from this depends the answer to your second question) is the EDMX is taken as is, this implies as a generated piece of code, you can refresh, destroy and recreate that every time you need or want without loosing any modification.
Now, as I said before, the nature of generated code, implies every change you made to the EDMX will be lost, so sure you can remove a property, but the model and db are not transparently in sync.
I think the best way to do that is
Even if this way could be a simplistic approach, doesnâ€™t cheating the nature of database first.
Just a note: working with database first, could be assisted by using partial classes to add things to the DbContext and entities involved to add functionalities and behaviours..