EF Feature CTP5: Pluggable Conventions

re: EF Feature CTP5: Pluggable Conventions

Shimmy Weitzhandler — Tue, 07 Feb 2012 02:37:14 GMT

Agree with Doug Clutter.

This feature is very compelling, and since it's not released with the RTW, this post should include a big red announcement on top of it that the info here wasn't release.

Very disapointing indeed, worked for half an hour making zillions of attributes now nothing works. I hate the fluent API. I like attributes. Clean code.

Here is an awsome workaround meanwhile: dotnetspeak.com/.../custom-conventions-in-entity-framework-code-first-v-4-1

Please vote here: data.uservoice.com/.../1155529-ability-to-plug-in-custom-conventions-for-schema-g

re: EF Feature CTP5: Pluggable Conventions

Doug Clutter — Tue, 19 Apr 2011 11:11:30 GMT

I'm having trouble creating a custom convention using v4.1 RTM. It appears that IConfigurationConvention is internal...and DbModelBuilder.Conventions does not have a public Add method.

If this functionality was removed from the RTM...would you please put a Big Darn Notice at the top of the article so peeps don't waste their time on this.

BTW, I am very bummed conventions were removed. They appeared to be the perfect answer to an issue I was struggling with. Hopefully, there will be a v4.2 that puts them back in. :)

re: EF Feature CTP5: Pluggable Conventions

Alan Cummings — Sun, 20 Feb 2011 21:26:14 GMT

This is great stuff - I love the ability to have simple POCO classes easily persistable. However, my preference is to have Entity Set names in the DB to be Singular... No problem you think, just remove the PluralizingTableNameConvention! But it doesn't work (when you set it to create the database) - it still creates pluralized Entity Set names.

I have managed to get around it by adding a convention:

public class SingularEntitySetNameConvention : IConfigurationConvention<Type, EntityTypeConfiguration> {

public void Apply(Type memberInfo, Func<EntityTypeConfiguration> configuration) {

configuration().ToTable(memberInfo.Name);

}

... and adding it in in the OnModelCreating override; but the PluralizingTableNameConvention will hopefully fixed for RTM.

Cheers, and keep up the good work :-D

re: EF Feature CTP5: Pluggable Conventions

Dirk Schomacker — Thu, 27 Jan 2011 17:35:56 GMT

Hi folks,

great work, but the mapping to a legacy foreignkey drives me totally crazy.

I tried nearly everything with annotations and removing default conventions but it doesn't work.

(I need annotations, cause I generate the Code with a t4 template)

Do you have a working example for me? (I tried "association" ,"foreignKey" and "column" annotations)

I simply want to map a foreign key to a custom fieldname in the database. This must be easy...i hope..

Thanks a lot, Dirk

re: EF Feature CTP5: Pluggable Conventions

shawn — Wed, 19 Jan 2011 04:55:23 GMT

It would be nice to see an example mapping a naming convention like ProductID = product_id, BrandName = brand_name, etc...

re: EF Feature CTP5: Pluggable Conventions

Anuj Pandey — Mon, 17 Jan 2011 09:06:33 GMT

I am using IgnoreAllTypesInNamespace as following and yet I see below error while reading employee from context. Any Suggestions ?

modelBuilder.Conventions.Add(new IgnoreAllTypesInNamespace(("e10.Objects")));

The mapping of CLR type to EDM type is ambiguous because multiple CLR types match the EDM type 'Employee'. Previously found CLR type 'e10.Data.Employee', newly found CLR type 'e10.Objects.Employee'.

re: EF Feature CTP5: Pluggable Conventions

Kris Vandermotten — Fri, 14 Jan 2011 16:21:41 GMT

Will this (or any other feature in this CTP) allow us to use managed types in the database, such as the spatial types included in SQL Server (or managed types we develop ourselves)?

re: EF Feature CTP5: Pluggable Conventions

Matthew Hail — Tue, 11 Jan 2011 14:00:40 GMT

The Entity method on ModelConfiguration is marked internal, making it impossible to map any simple entity types, while the complex method is public. Is this intentional? I need to call this method to be able to implement a schema tracking table similar to the IncludeMetadataConvention.

re: EF Feature CTP5: Pluggable Conventions

José Roberto Araújo — Tue, 11 Jan 2011 12:11:50 GMT

Hi Rowan,

I've been using the EF4 CTP5 and I could see that he has no way to update the database schema. I do not want it to delete the database, but update in accordance with the upgrades in my Model.

It´s possible in EF4 CTP5 version ???

Thank´s

re: EF Feature CTP5: Pluggable Conventions

Remco Blok — Tue, 11 Jan 2011 09:01:26 GMT

Hi Rowan,

I hope that for RTM the RIA Services team will be able to read information about the shape of your model so that it can automatically decorate properties with the Key and Association attributes required by RIA Services by implementing a DomainServiceDescriptionProvider. It would otherwise seem silly having to manually add these attributes for the sake of RIA Services when EF Code First can derive these configurations by convention. Mathew Charles mentioned in this thread here social.msdn.microsoft.com/.../57793bec-abc6-4520-ac1d-a63e40239aed that we can expect this in the future. However, after reading about the limitations in your post above about the RTM not allowing you to read information about the shape of your model, I wonder if the RIA Services team will be able to provide this with the RTM of EF Code First. Or can we read information about the model from ((IObjectContextAdapter)DbContext).DataContext.MetadataWorkspace? Can you tell me what we can expect for RTM regarding first class RIA Services support?

Thanks

Remco