1

Closed

EFDesigner - model first - we should let people know that the code will be generated only after they select EF version

description

In Model first we decided not to add templates to the project until the users selects the EF version s/he wants to work with. The reason for this is that we have different templates for EF6 and EF5 and until the user select which version will be used (which happens in the "create db wizard") we don't know which templates to add. This might be unexpected - especially for people who used previous versions of the designer. We should somehow let people know that it's OK not to have the code at this stage (note that even if the project compiled nothing would basically work since the database has not been created yet). One idea is to add a nested text file/template explaining that it is OK to not have templates and code generated before the db is generated.

Filing because I think 3 people already asked me about this even though we have not shipped it yet :)

Interesting scenario: What happens when I create a new model change the code generation strategy, create the database and will select EF6?
Closed Jul 25, 2013 at 12:04 AM by mgirgin

comments

RoMiller wrote Jul 22, 2013 at 7:19 PM

EF Team Triage: Update the comment in the stub code gen file 'This can occur when...'

BriceLambson wrote Jul 24, 2013 at 1:46 AM

Resolved with commit 516a5fc45b89 (EFTools repo)