Created Unassigned: Designer: Assert thrown when tests launch the model...
I am seeing this assert when the tests launch the model wizard. This is new, I haven't seen this before. ```---------------------------Assertion Failed: Abort=Quit, Retry=Debug,...
View ArticleEdited Issue: Designer: Assert thrown when tests launch the model wizard [1456]
I am seeing this assert when the tests launch the model wizard. This is new, I haven't seen this before. ```---------------------------Assertion Failed: Abort=Quit, Retry=Debug,...
View ArticleClosed Issue: Assert thrown when running P1 test case...
The test case has following assert twice. After clicking Ignore on it, the test case passes eventually. Here is the text from the Assert.```---------------------------Assertion Failed: Abort=Quit,...
View ArticleClosed Task: Designer should use EF6 for validating models. [1261]
At the moment Designer still uses EF5 for validating models. We should:- use EF6 for validating models- make sure that errors from reverse engineering are propagated to the rest of the stack or model...
View ArticleClosed Task: Update metadata API docs [788]
Some parts of the metadata API surface obtained from the MetadataWorkspace and now used when creating model-based Code First conventions are not well documented. Examples include:EntityType vs...
View ArticleCreated Unassigned: Pragma warning disable 1591 for DbMigration [1457]
Please, consider adding #pragma warning disable 1591 into auto generated DbMigrations.
View ArticleNew Post: Bug in TPT inheritance of EF6-beta1?
Hi, Lately I've been testing EF6 and I must say I'm very impressed with all the improvements! Can't wait for the RTM version to be shipped. While testing with EF6-Beta1 I think I found a bug. It's easy...
View ArticleEdited Issue: Code First models still get built more than once in EF6 [1454]
This is the default behavior of Code First in the standard flow of creating a model based on DbContext. The following code demonstrates by showing that a store model convention is applied...
View ArticleEdited Issue: Code First models still get built more than once in EF6 [1454]
This is the default behavior of Code First in the standard flow of creating a model based on DbContext. The following code demonstrates by showing that a store model convention is applied twice (I have...
View ArticleCreated Issue: "Sequence contains no elements" exception if all store model...
Note that this is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
Note that this is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
Note that this is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from the one...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from the one...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think this is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from the one...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think it is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from the one...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think it is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from the one...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
#SymptomsThis is a negative case but I think it is relatively easy to hit when fiddling with the model in model conventions. Adding an element to the storage model with a namespace name different from...
View ArticleEdited Issue: "Sequence contains no elements" exception if all store model...
This is a negative case but I think it is relatively easy to hit when fiddling with the metadata in store model conventions. Note that I have not tried yet to repro this on CSDL, but it is possible...
View ArticleCreated Unassigned: Malformed XML comment on DbModelExtensions.GetStoreModel...
The XML comment is missing the staring <summary> tag:```/// Gets the store model from the specified DbModel./// </summary>/// <param name="model">An instance of a class that...
View Article