You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you try to use the EF6 Designer on an SDK style project you will get a Null-Ref exception. This is because SDK-style projects are not supported. However, we should fail earlier and give a more helpful message. IE, show a dialog when the wizard is opened that says "SDK-Style projects are not supported in the EF6 Designer" or something to that effect. Alternatively we could try to not load the Designer options at all when in an SDK context (though I can see that leading to confusion where people think that the Designer is broken/missing as opposed to disabled).
The text was updated successfully, but these errors were encountered:
I vote for a message like: The EF6 Designer does not work with the current project type. Use a "classic" .NET Framework project type for Designer support.
Currently if you try to use the EF6 Designer on an SDK style project you will get a Null-Ref exception. This is because SDK-style projects are not supported. However, we should fail earlier and give a more helpful message. IE, show a dialog when the wizard is opened that says "SDK-Style projects are not supported in the EF6 Designer" or something to that effect. Alternatively we could try to not load the Designer options at all when in an SDK context (though I can see that leading to confusion where people think that the Designer is broken/missing as opposed to disabled).
The text was updated successfully, but these errors were encountered: