http://blogs.msdn.com/b/gduthie/archive/2006/10/03/faq-friday-recap.aspxI want to thank everyone who came out for our first FAQ Friday devBrainPick event last week. I especially appreciate everyone's patience with our format hiccups...this being a new series and format, I suppose that's to be expected. :-) We did haveen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/gduthie/archive/2006/10/03/faq-friday-recap.aspx#795248Fri, 06 Oct 2006 07:23:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:795248DEvHammer<p>Per the follow up from Eilon on the forum thread, this appears to be a bug in the XmlDataSource control. Changing the Data property should invalidate the cache, but doesn't.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=795248" width="1" height="1">http://blogs.msdn.com/b/gduthie/archive/2006/10/03/faq-friday-recap.aspx#788171Wed, 04 Oct 2006 03:02:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:788171Jun MengEvery time the page is "refreshed", a NEW XmlDataSource is created. Do we need disable caching for that new XmlDataSource? It does not make sense....<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=788171" width="1" height="1">