<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>IoC on Emad Alashi</title>
    <link>https://emadashi.com/tags/ioc/</link>
    <description>Recent content in IoC on Emad Alashi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 15 Jun 2015 14:04:27 +0000</lastBuildDate>
    <atom:link href="https://emadashi.com/tags/ioc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dependency Injection In ASP.NET 5 – One Step Deeper</title>
      <link>https://emadashi.com/2015/06/dependency-injection-in-asp-net-5-one-step-deeper/</link>
      <pubDate>Mon, 15 Jun 2015 14:04:27 +0000</pubDate>
      <guid>https://emadashi.com/2015/06/dependency-injection-in-asp-net-5-one-step-deeper/</guid>
      <description>&lt;p&gt;Dependency Injection has always been an integral part of all the web frameworks under the umbrella of the ASP.NET: Web API, SignalR, and MVC. But historically, these frameworks evolved separately from each other, hence each of these frameworks had its own way of supporting Dependency Injection, even with &lt;a href=&#34;https://katanaproject.codeplex.com/&#34; title=&#34;Katana&#34;&gt;Katana&lt;/a&gt;‘s trial to bring these frameworks together through &lt;a href=&#34;http://owin.org/&#34; title=&#34;OWIN&#34;&gt;OWIN&lt;/a&gt;, you still needed to do some hackery to have a unified container that supports them all at once. Well, things have changed!&lt;/p&gt;</description>
    </item>
    <item>
      <title>ANZCoders Wrapup</title>
      <link>https://emadashi.com/2015/06/anzcoders-wrapup/</link>
      <pubDate>Mon, 01 Jun 2015 23:43:45 +0000</pubDate>
      <guid>https://emadashi.com/2015/06/anzcoders-wrapup/</guid>
      <description>&lt;p&gt;Over the last week, the first &lt;a href=&#34;http://www.anzcoders.com/&#34;&gt;ANZCoders&lt;/a&gt; virtual conference was taking place, the conference that you can attend in your pyjamas! Fifteen sessions over five days by twelve speakers, all voted upon by the audience themselves.&lt;/p&gt;
&lt;p&gt;The conference was live, but it was recorded also on &lt;a href=&#34;https://www.youtube.com/channel/UCIVu42Uk-a6oFAflal8O-ag&#34;&gt;Youtube&lt;/a&gt;; every session has its own Youtube video available for watching any time. So I hear you say “Why attend live if the video is going to be available later?!”…here is why:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Data Access Within Business Objects -Bunian Design-</title>
      <link>https://emadashi.com/2008/11/data-access-within-business-objects-bunian-design/</link>
      <pubDate>Sun, 09 Nov 2008 21:17:27 +0000</pubDate>
      <guid>https://emadashi.com/2008/11/data-access-within-business-objects-bunian-design/</guid>
      <description>&lt;p&gt;In a previous post I showed the general architecture of Bunian. I&amp;rsquo;d like, in this post, to touch on the Data Access part and how it interacts with the Business Objects.&lt;/p&gt;
&lt;p&gt;In traditional architectures there are 3 known layers: Data Access, Business, and Presentation. &lt;a href=&#34;http://en.wikipedia.org/wiki/Data_Transfer_Object&#34;&gt;DTO&amp;rsquo;s&lt;/a&gt; (Data Transfer Objects) are used to carry the data back and forth between the layers. Look to the following diagram:&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;DTO&#34; loading=&#34;lazy&#34; src=&#34;http://eashi.files.wordpress.com/2008/11/dto.jpg&#34;&gt;&lt;/p&gt;
&lt;p&gt;Bunian contributors seemed to have the same experience developing against such architecture, so we have decided to go with something different; smart Business Objects with more toward OOP.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
