<?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/"
		>
<channel>
	<title>Comments on: ASP.NET MVC Pro&#8217;s and Con&#8217;s</title>
	<atom:link href="http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html</link>
	<description>Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools.</description>
	<lastBuildDate>Fri, 12 Mar 2010 14:26:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Frank</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-1629</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Thu, 29 Oct 2009 08:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-1629</guid>
		<description>MVC is an improvement compared to classic asp.

It offers a better framework to put everything in.

Compared to asp.net it has it&#039;s drawbacks.

Re-inventing the wheel is one of them.
Dirty asp-like spaghetti-code is another one.

The thing I especially don&#039;t like is that while asp.net uses an object-oriented approach to the controls (server controls), MVC has gone back to procedural controls (html helpers).

And for me this is a step back in software design.
Many things are no longer strongly typed and error prone.

I&#039;ve used MVC for a while now and frankly it&#039;s been a disappointment.
While it has it&#039;s uses for some things, for standard web-applications we will be going back to asp.net.</description>
		<content:encoded><![CDATA[<p>MVC is an improvement compared to classic asp.</p>
<p>It offers a better framework to put everything in.</p>
<p>Compared to asp.net it has it&#8217;s drawbacks.</p>
<p>Re-inventing the wheel is one of them.<br />
Dirty asp-like spaghetti-code is another one.</p>
<p>The thing I especially don&#8217;t like is that while asp.net uses an object-oriented approach to the controls (server controls), MVC has gone back to procedural controls (html helpers).</p>
<p>And for me this is a step back in software design.<br />
Many things are no longer strongly typed and error prone.</p>
<p>I&#8217;ve used MVC for a while now and frankly it&#8217;s been a disappointment.<br />
While it has it&#8217;s uses for some things, for standard web-applications we will be going back to asp.net.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slevdi Davoteca</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-1562</link>
		<dc:creator>Slevdi Davoteca</dc:creator>
		<pubDate>Mon, 03 Aug 2009 20:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-1562</guid>
		<description>&quot;...WebForms simply doesn’t fit in with the new demands of being unit testable ...&quot;

That is just not true.  Just look at the post by P. Haacked on MVP Supervisor:

http://tinyurl.com/of7rm

ASP.NET MVC is really good, but you can&#039;t use TDD as a pro over webforms development.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;WebForms simply doesn’t fit in with the new demands of being unit testable &#8230;&#8221;</p>
<p>That is just not true.  Just look at the post by P. Haacked on MVP Supervisor:</p>
<p><a href="http://tinyurl.com/of7rm" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/tinyurl.com/of7rm?referer=');">http://tinyurl.com/of7rm</a></p>
<p>ASP.NET MVC is really good, but you can&#8217;t use TDD as a pro over webforms development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aleemb</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-1363</link>
		<dc:creator>aleemb</dc:creator>
		<pubDate>Mon, 23 Feb 2009 09:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-1363</guid>
		<description>&gt; It’s partially my fault as well since I switched it from “8000 requests/sec” to “8000 times faster”. I screwed it up.

Why not fix it in the post? I happened to the read comments but most users won&#039;t and you are grossly misrepresenting the facts and misdirecting the readers.</description>
		<content:encoded><![CDATA[<p>&gt; It’s partially my fault as well since I switched it from “8000 requests/sec” to “8000 times faster”. I screwed it up.</p>
<p>Why not fix it in the post? I happened to the read comments but most users won&#8217;t and you are grossly misrepresenting the facts and misdirecting the readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeet</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-1021</link>
		<dc:creator>jeet</dc:creator>
		<pubDate>Fri, 28 Nov 2008 11:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-1021</guid>
		<description>I love webforms!</description>
		<content:encoded><![CDATA[<p>I love webforms!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zerga</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-820</link>
		<dc:creator>Zerga</dc:creator>
		<pubDate>Wed, 05 Nov 2008 15:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-820</guid>
		<description>I was wondering in what kind of trouble one gets into if considering to deploy a .NET MVC application on linux with mono... my guess is in the end you have another con (at least for a while) :/</description>
		<content:encoded><![CDATA[<p>I was wondering in what kind of trouble one gets into if considering to deploy a .NET MVC application on linux with mono&#8230; my guess is in the end you have another con (at least for a while) :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whatever</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-780</link>
		<dc:creator>whatever</dc:creator>
		<pubDate>Mon, 27 Oct 2008 20:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-780</guid>
		<description>I&#039;ve written VoiceXML applications using Classic ASP.  It is stupid to think Classic ASP can only output HTML.

Thus, MVC is more like Classic ASP/PHP than Webforms.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve written VoiceXML applications using Classic ASP.  It is stupid to think Classic ASP can only output HTML.</p>
<p>Thus, MVC is more like Classic ASP/PHP than Webforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Pang</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-775</link>
		<dc:creator>Kevin Pang</dc:creator>
		<pubDate>Fri, 24 Oct 2008 19:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-775</guid>
		<description>For me personally, the greatest pro as well as the greatest con for the ASP.NET MVC framework is the fact that it hasn&#039;t been fully flushed out yet.

That is, there isn&#039;t an agreed upon way to do things.  This is great in that it allows you to implement features in a way that makes sense for you and your application.  But it&#039;s also bad in that it greatly increases the learning curve and might make adoption of the framework a hard sell.

As an example, the ASP.NET web forms model has an easy to understand and easy to implement procedure for validation.  The ASP.NET MVC framework...not so much.  There are plenty of custom solutions out there which are arguably better than the ASP.NET web forms validators in that they allow you to hook into database events and put validation on your model instead of your UI, but again it comes at the price of ease of use.  I can see developers being very reluctant to have to research and develop custom solutions for things that normally come out of the box in development frameworks.</description>
		<content:encoded><![CDATA[<p>For me personally, the greatest pro as well as the greatest con for the ASP.NET MVC framework is the fact that it hasn&#8217;t been fully flushed out yet.</p>
<p>That is, there isn&#8217;t an agreed upon way to do things.  This is great in that it allows you to implement features in a way that makes sense for you and your application.  But it&#8217;s also bad in that it greatly increases the learning curve and might make adoption of the framework a hard sell.</p>
<p>As an example, the ASP.NET web forms model has an easy to understand and easy to implement procedure for validation.  The ASP.NET MVC framework&#8230;not so much.  There are plenty of custom solutions out there which are arguably better than the ASP.NET web forms validators in that they allow you to hook into database events and put validation on your model instead of your UI, but again it comes at the price of ease of use.  I can see developers being very reluctant to have to research and develop custom solutions for things that normally come out of the box in development frameworks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodrigo Diniz</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-773</link>
		<dc:creator>Rodrigo Diniz</dc:creator>
		<pubDate>Fri, 24 Oct 2008 10:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-773</guid>
		<description>Hi rob ...You do write more code using the mvc  and thats a fact, because you don&#039;t have to write the webform controls markup... you use drag and drop.
The code is a lot cleaner with the mvc and you do have less markup, but you have to write it without the help of any tool.</description>
		<content:encoded><![CDATA[<p>Hi rob &#8230;You do write more code using the mvc  and thats a fact, because you don&#8217;t have to write the webform controls markup&#8230; you use drag and drop.<br />
The code is a lot cleaner with the mvc and you do have less markup, but you have to write it without the help of any tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2008 October 24 - Links for today &#171; My (almost) Daily Links</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-772</link>
		<dc:creator>2008 October 24 - Links for today &#171; My (almost) Daily Links</dc:creator>
		<pubDate>Fri, 24 Oct 2008 07:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-772</guid>
		<description>[...] Young lists some ASP.NET MVC Pro’s and Con’s - read the comments too. They are a cracking [...]</description>
		<content:encoded><![CDATA[<p>[...] Young lists some ASP.NET MVC Pro’s and Con’s &#8211; read the comments too. They are a cracking [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: superjason</title>
		<link>http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html/comment-page-1#comment-770</link>
		<dc:creator>superjason</dc:creator>
		<pubDate>Fri, 24 Oct 2008 02:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html#comment-770</guid>
		<description>Mike, it depends what you&#039;re doing. There are helpers that minimize some of the tedious work. However, there are certainly scenarios where I would probably just go back to standard webforms. The true test will be to see what I tend to do once I am equally proficient with both.</description>
		<content:encoded><![CDATA[<p>Mike, it depends what you&#8217;re doing. There are helpers that minimize some of the tedious work. However, there are certainly scenarios where I would probably just go back to standard webforms. The true test will be to see what I tend to do once I am equally proficient with both.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
