<?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>Bitwise Gamgee &#187; postback</title>
	<atom:link href="http://blog.burcsade.com/tag/postback/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.burcsade.com</link>
	<description>I code, therefore I am</description>
	<lastBuildDate>Mon, 22 Mar 2010 08:17:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Preserving values of password fields after postback</title>
		<link>http://blog.burcsade.com/2009/08/18/preserving-values-of-password-fields-after-postback/</link>
		<comments>http://blog.burcsade.com/2009/08/18/preserving-values-of-password-fields-after-postback/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 12:31:53 +0000</pubDate>
		<dc:creator>laforge</dc:creator>
				<category><![CDATA[ASP.Net]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[csharp]]></category>
		<category><![CDATA[dotnet]]></category>
		<category><![CDATA[password field]]></category>
		<category><![CDATA[postback]]></category>

		<guid isPermaLink="false">http://blog.burcsade.com/?p=69</guid>
		<description><![CDATA[You have created your sign up form with full power of AJAX but when you do your trick to check for username availability via AJAX, it seems that passwords fields are reset. You can overcome this situation by setting up passwords filed values each time you make a postback.

1
txtPassword.Attributes.Add&#40;&#34;value&#34;, txtPassword.Text&#41;;

That should do the trick!


Bookmark It



















Hide [...]]]></description>
		<wfw:commentRss>http://blog.burcsade.com/2009/08/18/preserving-values-of-password-fields-after-postback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to disable button that causes postback in ASP.net</title>
		<link>http://blog.burcsade.com/2009/04/30/how-to-disable-button-that-causes-postback-in-aspnet/</link>
		<comments>http://blog.burcsade.com/2009/04/30/how-to-disable-button-that-causes-postback-in-aspnet/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 09:35:31 +0000</pubDate>
		<dc:creator>laforge</dc:creator>
				<category><![CDATA[ASP.Net]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[disable button]]></category>
		<category><![CDATA[postback]]></category>
		<category><![CDATA[vb]]></category>

		<guid isPermaLink="false">http://blog.burcsade.com/?p=18</guid>
		<description><![CDATA[You can disable a button on the client side to prevent multiple clicks by just adding an onClick function that runs on client side. You should check if page has a client side validation script and it passes first. If so, you just disable the button and call postback event.
Here is an example for the [...]]]></description>
		<wfw:commentRss>http://blog.burcsade.com/2009/04/30/how-to-disable-button-that-causes-postback-in-aspnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
