Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> Comments on: Entity Framework POCO (EF4): A Simple Mapping http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/?utm_source=rss&utm_medium=rss&utm_campaign=entity-framework-poco-ef4-a-simple-mapping Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53662 Jarod Ferguson Mon, 15 Feb 2010 22:47:38 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53662 <a href="#comment-53471" rel="nofollow">@mcsean</a> I have been meaning to give this a try and get back with you, but I have not been able to make the time yet. I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn't already) There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there. @mcsean
I have been meaning to give this a try and get back with you, but I have not been able to make the time yet.

I think RIA services is supposed to support POCOs ala NHibernate, so I imagine if you followed that track instead of the straight EF approach it could work. (If it doesn’t already)

There are supposedly new RIA services drops coming soon for the 2010RC, so look for improvements there.

]]> By: mcsean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-53471 mcsean Mon, 08 Feb 2010 15:16:53 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-53471 thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn't and the work around is to use presentation model. Can you please clarify that? thanks Jarod! Does the code-only work with WCF-RIA-Services? I once read a post from a forum and someone said it doesn’t and the work around is to use presentation model. Can you please clarify that?

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52386 Jarod Ferguson Mon, 04 Jan 2010 19:58:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52386 @mcsean - it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed). @jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that. @emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx @mcsean – it gives you total control over your entities: Persistence ingnorance, greater testability, finer control over mapping strategies, no code generation (so it works much better with source control), and no GUI desginer so it works better with large models (There is nothing like rebuilding a model with 50-100 entities because the designer failed).

@jason not sure I compeletely follow? Do you mean a convention so it automatically maps the properties to the columns if they are the same name? I remember seeing something that did that.

@emanuele Yes, it handles both of those scenarios. Check out this post here: http://blogs.msdn.com/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx

]]> By: emanuele http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52244 emanuele Fri, 01 Jan 2010 09:26:05 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52244 Very interesting post. I have a question: can I map an entity property using a different column names with EntityConfiguration? and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it? Very interesting post.
I have a question:
can I map an entity property using a different column names with EntityConfiguration?
and if I have a complex type in the entity (like Team.Address wich has different properties), how can I map it?

]]> By: t http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-52017 t Mon, 28 Dec 2009 04:29:29 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-52017 T T

]]> By: Jason Grundy http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51910 Jason Grundy Sat, 26 Dec 2009 17:04:44 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51910 Great intro. I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can't help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root. Great intro.

I agree with Tony that it looks very Fluent NHibernate-esque. Given my experience there I can’t help but wonder if there are naming conventions that can be defined at a global level that would avoid an override for every aggregate root.

]]> By: McSean http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-2/#comment-51779 McSean Wed, 23 Dec 2009 07:01:59 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51779 I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me? I knew that the new VS2010 and EF4 come with a template to generate POCO objects. so what is the advantage that code-only option can offer me?

]]> By: Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51449 Elegant Code » Building a Unity Extension for Entity Framework POCO Configuration, Repository and Unit of Work Wed, 16 Dec 2009 00:35:23 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51449 [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...] [...] my previous two posts I talk about simple EF4 mappings and some common abstractions I like to work with for my entity persistence operations. In this post [...]

]]> By: Jarod Ferguson http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51446 Jarod Ferguson Tue, 15 Dec 2009 21:20:32 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51446 @isamux - A few issues I encountered: - I wanted to specify the name (or convention) of FK Id's. , e.g TeamId. I had to change the name in the Database to "Team_ID". In FNH you could just specify the Key name when mapping the relationship. - I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection. Perhaps these are supported, but I could figure it out. @isamux – A few issues I encountered:
- I wanted to specify the name (or convention) of FK Id’s. , e.g TeamId. I had to change the name in the Database to “Team_ID”. In FNH you could just specify the Key name when mapping the relationship.

- I wanted to have a private collection for the team Players, exposing only a getter for the collection, but I was only able to map using an AutoMatic property, therefore losing encapsulation on the collection.

Perhaps these are supported, but I could figure it out.

]]> By: isamux http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/comment-page-1/#comment-51444 isamux Tue, 15 Dec 2009 21:09:39 +0000 http://elegantcode.com/2009/12/15/entity-framework-poco-ef4-a-simple-mapping/#comment-51444 Nice introduction to the new POCO feature of EF4. Could you name some of the 'quite a few common scenarios which are not yet supported'? Nice introduction to the new POCO feature of EF4.
Could you name some of the ‘quite a few common scenarios which are not yet supported’?

]]>