<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>thekua.com@work &#187; Web Development</title>
	<atom:link href="http://www.thekua.com/atwork/category/web-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thekua.com/atwork</link>
	<description>thekua&#039;s reflections on work related topics</description>
	<lastBuildDate>Tue, 27 Jul 2010 06:42:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Getting NUnit ASP to work with .Net 2.0</title>
		<link>http://www.thekua.com/atwork/2007/02/getting-nunit-asp-to-work-with-net-20/</link>
		<comments>http://www.thekua.com/atwork/2007/02/getting-nunit-asp-to-work-with-net-20/#comments</comments>
		<pubDate>Mon, 12 Feb 2007 09:09:47 +0000</pubDate>
		<dc:creator>Patrick</dc:creator>
				<category><![CDATA[.Net]]></category>
		<category><![CDATA[ASP]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=14</guid>
		<description><![CDATA[On my current project we’ve been having a pretty good experience leveraging the NUnitASP library for automated testing of our website. In our second week of development, we noticed like many other people, that it is yet fully compatible with .Net 2.0 because of the way that ASP.Net now generates its javascript postback functions. In [...]]]></description>
			<content:encoded><![CDATA[<p>On my current project we’ve been having a pretty good experience leveraging the <a href="http://nunitasp.sourceforge.net">NUnitASP library</a> for automated testing of our website. In our second week of development, we noticed like many other people, that it is yet fully compatible with .Net 2.0 because of the way that ASP.Net now generates its javascript postback functions. </p>
<p>In the previous .Net version, ASP.Net seemed to generate a very simple function of the form of <code>__doPostBack([targetId], [targetArguments]) </code> that would effectively set two hidden variables (<code>__EVENTTARGET</code> and <code>__EVENTARGUMENT</code> respectively). In the current version, ASP.Net generates a much more complex javascript function (called <code>WebForm_DoPostBackWithOptions</code>) that I think is caused with use of any of the ASP validator components. </p>
<p>One work around that <a href="http://weblogs.asp.net/lancea/default.aspx" rel="nofollow">one person (Lance Ahlberg)</a> found was to turn the “<code>CausesValidation</code>” property off for controls but this may or may not suit the way that you are developing your website. Looking at what the javascript generated does, I think that there must have been a better solution so I spent some time delving into the depths of NUnit ASP to find one. </p>
<p>The result is a patch to <code>ControlTester.cs</code> that allows the <code>__EVENTTARGET</code> and <code>__EVENTARGUMENT</code> to still be set by extracting out the appropriate values from the new <code>WebForm_DoPostBackWithOptions</code> javascript function. You can download the patch <a href="http://www.thekua.com/atwork/wp-content/uploads/2007/02/ControlTester.patch">here</a> but you have to build your own NUnit ASP, or wait until this is integrated with the next release. The ticket for my submission can be found <a href="http://sourceforge.net/tracker/index.php?func=detail&#038;aid=1657809&#038;group_id=49940&#038;atid=458032">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thekua.com/atwork/2007/02/getting-nunit-asp-to-work-with-net-20/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
