Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Any experiences on how to document Entity Framework 4 based Database projects?
There is the Document and Summary properties on the Entities, but if we want to regenerate the model from the database at some point, it will be lost!
Is there some way to map documentation data inside SQL to the Entities in the EDMX file so it is safe.
Suggestions of other best practices? Ideally I want to be able to augo generate html/helpfile documentation from the DB when we deploy.
Your statement that CSDL (part of EDMX) changes will be lost if you regenerate is incorrect. This is not LINQ to SQL. CSDL changes are retained during an update.