<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by Jalal</title>
    <description>Stories kicked by Jalal</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Debate: Do We Really Need Three Layer Architecture?</title>
      <description>How many of you changed your database vendor (i.e. Sql Server, Access) after developing an application? How many of your data entities include business logic? I could say, less than 10% in both cases for my case. I found the similar statistics for my other known developers. I guess this is true for less that 10% of the developers around the world.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fforums.asp.net%2ft%2f1343018.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fforums.asp.net%2ft%2f1343018.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/adonet/Debate_Do_We_Really_Need_Three_Layer_Architecture</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/adonet/Debate_Do_We_Really_Need_Three_Layer_Architecture</guid>
      <pubDate>Wed, 05 Nov 2008 21:46:09 GMT</pubDate>
    </item>
    <item>
      <title>.NET Application Modeling Language (nAML) Specification and Tools </title>
      <description>Understanding the architecture and code in software application plays as major factors while building good software products. This free e-book introduces a new visual modeling technique, termed as "nAML" (.NET Application Modeling Language) which overcomes the limitation of typical modeling languages by providing revolutionary way!

Nothing much to say, just download it and you can get to know how POWERFUL it is! &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcode.msdn.microsoft.com%2fProject%2fDownload%2fFileDownload.aspx%3fProjectName%3dnaml%26DownloadId%3d3083"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcode.msdn.microsoft.com%2fProject%2fDownload%2fFileDownload.aspx%3fProjectName%3dnaml%26DownloadId%3d3083" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/NET_Application_Modeling_Language_nAML_Specification_and_Tools</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/NET_Application_Modeling_Language_nAML_Specification_and_Tools</guid>
      <pubDate>Thu, 11 Sep 2008 15:31:03 GMT</pubDate>
    </item>
    <item>
      <title>10 Tools Which I Still Use, Even I Have VSTS 2008</title>
      <description>In my last post, titled &amp;quot;10 Tools Which I Left After Using VSTS 2008&amp;quot;,  I have included a list of 10 tools which I am not using currently, as I have the corresponding features available in Visual Studio Team System 2008. However, on the other hand, I am still using few tools even I have VSTS 2008! &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fweblogs.asp.net%2fashraful%2farchive%2f2008%2f06%2f24%2f10-tools-which-i-still-use-even-i-have-vsts-2008.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fweblogs.asp.net%2fashraful%2farchive%2f2008%2f06%2f24%2f10-tools-which-i-still-use-even-i-have-vsts-2008.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/10_Tools_Which_I_Still_Use_Even_I_Have_VSTS_2008</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/10_Tools_Which_I_Still_Use_Even_I_Have_VSTS_2008</guid>
      <pubDate>Wed, 25 Jun 2008 15:31:11 GMT</pubDate>
    </item>
    <item>
      <title>Employee Info ASP.NET Starter Kit </title>
      <description>This is a starter kit, which includes very simple user requirements, where we can create, read, update ad delete (crud) the employee info of a company.

The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing new asp.net 2.0 and sql server 2005 features, as well as latest best coding practices. 

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcode.msdn.microsoft.com%2feisk"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcode.msdn.microsoft.com%2feisk" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/Employee_Info_ASP_NET_Starter_Kit</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/Employee_Info_ASP_NET_Starter_Kit</guid>
      <pubDate>Wed, 09 Apr 2008 09:42:46 GMT</pubDate>
    </item>
  </channel>
</rss>