http://blogs.msdn.com/webnext/archive/tags/Vittorio/default.aspxTags: Vittorioen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/webnext/archive/2007/03/30/wpf-e-part-of-a-bigger-ecosystem.aspxFri, 30 Mar 2007 22:47:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:1995573lmoroney@microsoft.com0http://blogs.msdn.com/webnext/comments/1995573.aspxhttp://blogs.msdn.com/webnext/commentrss.aspx?PostID=1995573http://blogs.msdn.com/webnext/rsscomments.aspx?PostID=1995573<P>The neat thing about WPF/E is that it is not a standalone technology. It is based on standard, open, technologies such as XML (for XAML) and JavaScript (for programming). </P> <P>This opens up some wonderful opportunities for integrating WPF/E with other applications, or building it neatly into existing infrastructures. </P> <P>For one nice example, check out my friend Vittorio's blog, where he has put together a super cool WPF/E + Cardspace integration sample. Over the next few weeks I'll be publishing some more samples of WPF/E with ASP.NET, with AJAX etc. </P> <P>Here's the link: </P> <P class=MsoNormal style="MARGIN: 0in 0in 0pt"><A href="http://blogs.msdn.com/vbertocci/archive/2007/03/28/wpf-e-and-windows-cardspace-or-plugging-ria-in-the-identity-metasystem.aspx"><FONT face=Calibri size=3>http://blogs.msdn.com/vbertocci/archive/2007/03/28/wpf-e-and-windows-cardspace-or-plugging-ria-in-the-identity-metasystem.aspx</FONT></A><FONT face=Calibri size=3> </FONT></P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1995573" width="1" height="1">WPF/EWeb.NEXTVittorioCardspaceArchitecture