<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: MVC Project Architecture</title>
	<atom:link href="http://blog.coreycoogan.com/2009/06/05/mvc-project-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.coreycoogan.com/2009/06/05/mvc-project-architecture/</link>
	<description>Python, .Net, C#, ASP.NET MVC, Architecture and Design</description>
	<lastBuildDate>Tue, 07 Feb 2012 04:33:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: coreycoogan</title>
		<link>http://blog.coreycoogan.com/2009/06/05/mvc-project-architecture/#comment-60</link>
		<dc:creator><![CDATA[coreycoogan]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:12:33 +0000</pubDate>
		<guid isPermaLink="false">http://coreycoogan.wordpress.com/?p=24#comment-60</guid>
		<description><![CDATA[Hi Josh,
    the project I outlined here changed quite a bit after I was pulled away from it.  The architect had different ideas about what a layered application looks like and the team was rather junior, resulting  poor man&#039;s DI rather than using the StructureMap container that was already available to the project.  Everything that I wrote, however, leveraged SM for all DI.  Check out my &lt;a href=&quot;http://blog.coreycoogan.com/2009/11/06/castle-windsor-tutorial-in-asp-net-mvc/&quot; rel=&quot;nofollow&quot;&gt;post on Castle&lt;/a&gt; to see how I&#039;m doing that stuff in latest project.

LLBLGen is a pretty good ORM, although I like SubSonic more.  Unfortunately, the team decided that EntityFramework was better than LLBLGen and decided to use that later in the project.  I absolutely hate EF and think LLBLGen is a much stronger ORM, but it wasn&#039;t my call.

As far as your transactions go, I think your architecture may be causing you these hassles.  First, you adapter should probably be in an Infrastructure layer, not your Core layer.  Your Core layer should be your Domain objects, or in this case LLBLGen entities.  You would then have an Application Layer that provides application services.  It is these services that would be responsible for opening the transaction, calling the applicable operations (passing the repository or transaction) and then committing.  I would steer clear from managing transactions in the UI.]]></description>
		<content:encoded><![CDATA[<p>Hi Josh,<br />
    the project I outlined here changed quite a bit after I was pulled away from it.  The architect had different ideas about what a layered application looks like and the team was rather junior, resulting  poor man&#8217;s DI rather than using the StructureMap container that was already available to the project.  Everything that I wrote, however, leveraged SM for all DI.  Check out my <a href="http://blog.coreycoogan.com/2009/11/06/castle-windsor-tutorial-in-asp-net-mvc/" rel="nofollow">post on Castle</a> to see how I&#8217;m doing that stuff in latest project.</p>
<p>LLBLGen is a pretty good ORM, although I like SubSonic more.  Unfortunately, the team decided that EntityFramework was better than LLBLGen and decided to use that later in the project.  I absolutely hate EF and think LLBLGen is a much stronger ORM, but it wasn&#8217;t my call.</p>
<p>As far as your transactions go, I think your architecture may be causing you these hassles.  First, you adapter should probably be in an Infrastructure layer, not your Core layer.  Your Core layer should be your Domain objects, or in this case LLBLGen entities.  You would then have an Application Layer that provides application services.  It is these services that would be responsible for opening the transaction, calling the applicable operations (passing the repository or transaction) and then committing.  I would steer clear from managing transactions in the UI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://blog.coreycoogan.com/2009/06/05/mvc-project-architecture/#comment-59</link>
		<dc:creator><![CDATA[Josh]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 06:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://coreycoogan.wordpress.com/?p=24#comment-59</guid>
		<description><![CDATA[How is the project going?  We&#039;ve been using LLBLGen in an ASP.NET MVC project for a large business services app for the past 6 months and are pretty happy with it so far.  Out of curiosity, are you using an IoC framework (like StructureMap or Unity), or just injecting the various dependencies manually through default c-tors?  Also, how are you handling transactions?  So far that&#039;s been our biggest struggle since the trx often must reside at the controller/session level, but the adapter is down in our service layer (your app.core layer).  

Good luck!]]></description>
		<content:encoded><![CDATA[<p>How is the project going?  We&#8217;ve been using LLBLGen in an ASP.NET MVC project for a large business services app for the past 6 months and are pretty happy with it so far.  Out of curiosity, are you using an IoC framework (like StructureMap or Unity), or just injecting the various dependencies manually through default c-tors?  Also, how are you handling transactions?  So far that&#8217;s been our biggest struggle since the trx often must reside at the controller/session level, but the adapter is down in our service layer (your app.core layer).  </p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

