http://blogs.msdn.com/b/brada/archive/2003/05/31/50062.aspxThe other day at the Triangle Area . NET Users Group someone asked me an interesting question. &#160; Based on my experience at Microsoft working on future versions on the . NET Framework and the Windows operating system, what should developers doen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/brada/archive/2003/05/31/50062.aspx#6802168Wed, 19 Dec 2007 06:58:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:6802168Chris Love's Official Blog - Professional ASP.NET<p>For some reason I started reviewing some of my friend's Brad Abrams old Blog entries. It was one of those</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=6802168" width="1" height="1">http://blogs.msdn.com/b/brada/archive/2003/05/31/50062.aspx#187067Mon, 19 Jul 2004 05:20:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:187067selinawe should do full preparation for the future !we can develop all kinds of qualification to wellcom our new challengen !<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=187067" width="1" height="1">http://blogs.msdn.com/b/brada/archive/2003/05/31/50062.aspx#50063Wed, 04 Jun 2003 16:00:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:50063Scott GallowayThe Application Architecture points from point 2...are you really advocating using XML in cross machine communication within an organisation? I can see the point in this for the Business Layer -&gt; Presentation layer communication - since you could more simple change the presentation layer, but for data access this adds huge overhead to what is generally already the most congested pipe... I guess Yukon will make this easier to do (i.e., XML as the primary data access mode) - but I don't think most applications really need it!<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=50063" width="1" height="1">