<?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: Validation In Monorail</title>
	<atom:link href="http://winterdom.com/2007/08/validationinmonorail/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2007/08/validationinmonorail</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Thu, 11 Mar 2010 20:28:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2007/08/validationinmonorail/comment-page-1#comment-574</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Wed, 15 Aug 2007 19:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/08/validationinmonorail#comment-574</guid>
		<description>@Yartz: I realize this sounds like a lot of steps, but in the end it turns out pretty easy once you get the hang of it. Notice, however, that a lot of the steps I outlines really have little to do with validation per-se; they are added to enable databinding and other stuff. Certainly, if you described the entire process for ASP.NET validators, it would also contain a lot of steps; it&#039;s not really just drag and drop the validator component and that&#039;s it.
Besides, I&#039;ve personally have had horrendous experience with the built-in asp.net validator framework; so much that in one project I participated they ended up writing their own.
</description>
		<content:encoded><![CDATA[<p>@Yartz: I realize this sounds like a lot of steps, but in the end it turns out pretty easy once you get the hang of it. Notice, however, that a lot of the steps I outlines really have little to do with validation per-se; they are added to enable databinding and other stuff. Certainly, if you described the entire process for ASP.NET validators, it would also contain a lot of steps; it&#8217;s not really just drag and drop the validator component and that&#8217;s it.<br />
Besides, I&#8217;ve personally have had horrendous experience with the built-in asp.net validator framework; so much that in one project I participated they ended up writing their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yartz</title>
		<link>http://winterdom.com/2007/08/validationinmonorail/comment-page-1#comment-573</link>
		<dc:creator>yartz</dc:creator>
		<pubDate>Wed, 15 Aug 2007 18:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/08/validationinmonorail#comment-573</guid>
		<description>Monorail is such a relief from the pain that is ASP.Net. Now, instead of the horrid integrated ASP.Net validation controls you have attributes, inheritance, yet another tag soup language, inline loops, conditionals all over the place, terabytes of yet another javascript library, all this tightly wrapped in 9 steps to get the whole thing - hopefully - working.
It&#039;s almost as beautiful as the NIH/non ASP.Net rendering model used in CruiseControl.Net web dashboard. So simple and extensible that it takes two to three years to get some changes done (and the whole thing is dead slow, but cache is coming, soon, really).
</description>
		<content:encoded><![CDATA[<p>Monorail is such a relief from the pain that is ASP.Net. Now, instead of the horrid integrated ASP.Net validation controls you have attributes, inheritance, yet another tag soup language, inline loops, conditionals all over the place, terabytes of yet another javascript library, all this tightly wrapped in 9 steps to get the whole thing &#8211; hopefully &#8211; working.<br />
It&#8217;s almost as beautiful as the NIH/non ASP.Net rendering model used in CruiseControl.Net web dashboard. So simple and extensible that it takes two to three years to get some changes done (and the whole thing is dead slow, but cache is coming, soon, really).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
