<?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: dotNet Application Framework</title>
	<atom:link href="http://maonet.wordpress.com/2008/03/27/dotnet-application-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://maonet.wordpress.com/2008/03/27/dotnet-application-framework/</link>
	<description>IOC(SM):MOC(RM):TDD(NU):SCC(TFS):ORM(L2S):JSL(Jq):CIS(CC)</description>
	<lastBuildDate>Thu, 19 Nov 2009 19:41:20 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Video &#8211; Reuni&#243;n ALT .NET Caf&#233; 29 De Agosto &#171; BeyondNet</title>
		<link>http://maonet.wordpress.com/2008/03/27/dotnet-application-framework/#comment-597</link>
		<dc:creator>Video &#8211; Reuni&#243;n ALT .NET Caf&#233; 29 De Agosto &#171; BeyondNet</dc:creator>
		<pubDate>Fri, 04 Sep 2009 06:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://maonet.wordpress.com/?p=96#comment-597</guid>
		<description>[...] dotNet Application Framework [...]</description>
		<content:encoded><![CDATA[<p>[...] dotNet Application Framework [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ish Singh</title>
		<link>http://maonet.wordpress.com/2008/03/27/dotnet-application-framework/#comment-273</link>
		<dc:creator>Ish Singh</dc:creator>
		<pubDate>Fri, 04 Apr 2008 18:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://maonet.wordpress.com/?p=96#comment-273</guid>
		<description>Hello, Since there is good and useful information about different frameworks here I thought I&#039;ll add information about the Quick Objects Business Logic Framework as well. Quick Objects is a radically different approach but has some similarities with CSLA. The main similarity is that it is not completely dependent on code generation, and it is rather a framework. QO consists of reusable libraries that are usable without generating any code at all. However, the included Designer application makes it super easy to generate the classes that extend the power of the framework. So essentially the developer is immediately productive using QO. There is no hassle of maintaining templates and no external tools/templates are needed.

The other big difference is that the QO&#039;s focus is keeping it simple, flexible and keep up the high performance. The business objects generated by QO allow the developer to decide what to select, search, sort, group etc in a very easy way. Also, instead of having a &quot;lazy load&quot; feature where the developer does not have control on what all will be loaded, QO rather has smart loading. For example, if you needed OrderItem, Order, Customer, and CustomerType information, instead of making 4 calls to the database QO can do it in one, and you still have control over what fields get loaded/selected. Similar possibility with multi level joins and searches. Same approach with concurrency management, instead of forcing the developer to choose between Optimistic or Pessimistic, the developer can choose what he/she wants and how (for example may be the developer does not want to include a binary field in concurrency check).

The biggest difference is that QO is not just limited to CRUD, it has other capabilities such as ability to work in a disconnected environment and reconnecting/saving at a later time. Then the validation framework is the cherry on top. So with QO you don&#039;t need to worry about data access, rather you can concentrate on implementing your logic and validation rules and creating user interfaces.

And our &lt;a href=&quot;http://www.akaltech.com/Products/Business_Logic/Details/Details.aspx&quot; rel=&quot;nofollow&quot;&gt;framework&lt;/a&gt; and &lt;a href=&quot;http://www.akaltech.com/Products/Web_Data_Source/Details/Details.aspx&quot; rel=&quot;nofollow&quot;&gt;Data Source for ASP.NET&lt;/a&gt; works with almost all third party user interface controls.

QO has been thoroughly tested and perfected over the years and it is fully supported. We probably have one of the best response times for support requests :) QO is gaining more popularity as people get frustrated with the other approaches and need something flexible and easier to use.  In no means I am saying that other approaches are bad, everything has its own +/-

Thanks,
Ish Singh

Akal Tech
Quick Objects - Faster Way To Powerful Applications
http://www.akaltech.com</description>
		<content:encoded><![CDATA[<p>Hello, Since there is good and useful information about different frameworks here I thought I&#8217;ll add information about the Quick Objects Business Logic Framework as well. Quick Objects is a radically different approach but has some similarities with CSLA. The main similarity is that it is not completely dependent on code generation, and it is rather a framework. QO consists of reusable libraries that are usable without generating any code at all. However, the included Designer application makes it super easy to generate the classes that extend the power of the framework. So essentially the developer is immediately productive using QO. There is no hassle of maintaining templates and no external tools/templates are needed.</p>
<p>The other big difference is that the QO&#8217;s focus is keeping it simple, flexible and keep up the high performance. The business objects generated by QO allow the developer to decide what to select, search, sort, group etc in a very easy way. Also, instead of having a &#8220;lazy load&#8221; feature where the developer does not have control on what all will be loaded, QO rather has smart loading. For example, if you needed OrderItem, Order, Customer, and CustomerType information, instead of making 4 calls to the database QO can do it in one, and you still have control over what fields get loaded/selected. Similar possibility with multi level joins and searches. Same approach with concurrency management, instead of forcing the developer to choose between Optimistic or Pessimistic, the developer can choose what he/she wants and how (for example may be the developer does not want to include a binary field in concurrency check).</p>
<p>The biggest difference is that QO is not just limited to CRUD, it has other capabilities such as ability to work in a disconnected environment and reconnecting/saving at a later time. Then the validation framework is the cherry on top. So with QO you don&#8217;t need to worry about data access, rather you can concentrate on implementing your logic and validation rules and creating user interfaces.</p>
<p>And our <a href="http://www.akaltech.com/Products/Business_Logic/Details/Details.aspx" rel="nofollow">framework</a> and <a href="http://www.akaltech.com/Products/Web_Data_Source/Details/Details.aspx" rel="nofollow">Data Source for ASP.NET</a> works with almost all third party user interface controls.</p>
<p>QO has been thoroughly tested and perfected over the years and it is fully supported. We probably have one of the best response times for support requests <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  QO is gaining more popularity as people get frustrated with the other approaches and need something flexible and easier to use.  In no means I am saying that other approaches are bad, everything has its own +/-</p>
<p>Thanks,<br />
Ish Singh</p>
<p>Akal Tech<br />
Quick Objects &#8211; Faster Way To Powerful Applications<br />
<a href="http://www.akaltech.com" rel="nofollow">http://www.akaltech.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
