<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AutoMapper on InternetException</title><link>https://internetexception.com/tags/automapper/</link><description>Recent content in AutoMapper on InternetException</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 23 Feb 2020 13:54:31 +0100</lastBuildDate><atom:link href="https://internetexception.com/tags/automapper/index.xml" rel="self" type="application/rss+xml"/><item><title>Entity Framework and Base Entity class</title><link>https://internetexception.com/2013/05/16/entity-framework-and-base-entity-class/</link><pubDate>Thu, 16 May 2013 14:32:00 +0200</pubDate><guid>https://internetexception.com/2013/05/16/entity-framework-and-base-entity-class/</guid><description>&lt;p&gt;Entity Framework does great job with taking care of entities changes and entities collection internally. And its uses almost plain POCO objects. Almost because collections of dependents data like in 1 to many tables relationship needs virtual keyword. Its understandable since EF needs to track what happens to collection. For instance lets have 2 tables: Customer and dependent Order. &lt;a class="img-zoom" href="https://internetexception.com/wp-content/uploads/2013/05/customer_order.png"&gt;&lt;img&#10; src="https://internetexception.com/wp-content/uploads/2013/05/customer_order.png"&#10; alt=""&#10; &#10; loading="lazy" decoding="async"&gt;&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>