<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The All-Avalon, All-the-time Application</title><link>http://blogs.msdn.com/johngossman/archive/2005/09/26/473911.aspx</link><description>Expression Interactive Designer (aka Sparkle) is a 100% .NET, managed code application. The source is currently more than 1200 .cs files and about 140 .xaml files totally 210,000 some lines of C# and 23,000 some lines of XAML. There is no unmanaged code</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: The All-Avalon, All-the-time Application</title><link>http://blogs.msdn.com/johngossman/archive/2005/09/26/473911.aspx#478108</link><pubDate>Fri, 07 Oct 2005 07:13:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:478108</guid><dc:creator>jmacdonagh</dc:creator><description>I understand the need for the HtmlHelp call, and I understand the desire to utilize Microsoft's HTML Help framework, but why not replace all those ugly help files with a flashy help file using Avalon's document features? Either that, or talk to the WinFX team about putting in a managed wrapper around it.</description></item><item><title>re: HTMLHelp</title><link>http://blogs.msdn.com/johngossman/archive/2005/09/26/473911.aspx#478236</link><pubDate>Fri, 07 Oct 2005 17:59:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:478236</guid><dc:creator>JohnGossman</dc:creator><description>The tools and infrastructure for a replacement for HTML help will take time to build.  I think the WinFX team is ambivalent about adding another wrapper (since one already exists in WinForms) when we don't know whether HTMLHelp is the right long term strategy.</description></item><item><title>Dogfooding WPF at MS</title><link>http://blogs.msdn.com/johngossman/archive/2005/09/26/473911.aspx#740111</link><pubDate>Tue, 05 Sep 2006 00:52:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:740111</guid><dc:creator>Raimond Brookman</dc:creator><description>Microsoft has used Avalon internally already for a major application: Sparkle. Expression Interactive</description></item><item><title>Sparkle - the 100% All-Managed, All-WPF Application</title><link>http://blogs.msdn.com/johngossman/archive/2005/09/26/473911.aspx#8665914</link><pubDate>Sun, 29 Jun 2008 06:40:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8665914</guid><dc:creator>DEVELOPMENT SITE - NOT MY PUBLIC BLOG</dc:creator><description>&lt;p&gt;In case anyone ever wonders if Microsoft produces any real apps (other than Microsoft Max ) using managed code, here you go: Expression Interactive Designer (aka Sparkle) is a 100% .NET, managed code application. The source is currently more than 1200&lt;/p&gt;
</description></item></channel></rss>