Toolkit Extender for creating WPF/E components


If you haven’t already seen ScottGu’s post on WPF/E, I’d recommend checking it out.  WPF/E is a new technology that opens up incredible new possibilities for improving the richness and interactivity of the web.  Scott links to a few demos, and the WPF/E install is quick simple, and even works on a Mac!


Adding a WPF/E component to your page is still a little bit of work though.  To make it easier, I’ve created a simple Toolkit extender that automates this code so you can just create the extender and go.  See the attached file below – there is a C# and a VB.Net version of the component (though if you’re just using the extender, it doesn’t matter).


To add WPF/E to your website:




    1. Create your XAML file (there is a simple XAML file in the sample attached, otherwise you can use the Expression Interactive Designer beta).  Add the file to your website.  Also add any other scriptiing you’d like for your WPF/E component.

    2. Build the attached solution and add the WPFEHost DLL to your website’s bin directory (you’ll also need to add AjaxControlToolkit.dll if you don’t already have it).

    3. In your website, create a Panel where you want the WPF/E content to show.  

    4. Add the WPFEHost extender.  Note that if you’re writing any script against your WPF/E control, the ID of the WPF/E control will be set to the ID of Extender, for example “wpfeControl” below.


<wpfe:WPFEHostExtender ID=”wpfeControl Runat=”server” Height=”350px” TargetControlID=”Panel1 Width=”350px” XamlPath=”myWpfeControl.xaml” BackgroundColor=”transparent”/>


That’s it! 


 

WPFEHostExtender.zip


Comments (19)

  1. Prog says:

    If you haven’t already seen ScottGu’s post on WPF/E , I’d recommend checking it out. WPF/E is a new technology

  2. Kudos to the ASP.NET AJAX Toolkit team for creating a killer extender to simplify getting a "WPF/E" control

  3. A few links I have collected for your WPFE journey. John Rayner on WPFE and IE security (this will

  4. Nikhil Kothari has a sample that demonstrates Script# and “WPF/E” integration. Shawn Burke posted a Toolkit

  5. bleroy says:

    Quick question: why does it have to be an extender and not a simple control?

  6. sburke says:

    No real reason – going the extender route was quicker since we have the templates, etc. for it.  It could just as easily be a control.

  7. 新 PC への移行作業中でのんびりとは読めなかったのですが、ASP.NET と WPF/E は今後連携して利用していく事が可能になるようですね(統合して開発していく事が可能になるようです。) WPF/E

  8. E&rsquo; di qualche giorno fa l&rsquo;annuncio dell&rsquo;uscita della CTP di Dicembre di WPF/E . E&rsquo;

  9. cpjolly says:

    Shawn, do you plan to update this for AJAX 1.0 RC ?

    Thanks

  10. PinalBhatt says:

    Hello Shawn

    Any plan for updating this(Toolkit Extender for creating WPF/E components) to ASP.Net AJAX 1.0 RC and WPF/E Dec06 CTP

  11. PinalBhatt says:

    Actual i was trying to compile WPFEHostExtender website and WPFEHost class library with ASP.Net AJAX RC1.

    Any way i could compile WPFEHost class library by (1) changing refercences to new AjaxControlToolkit.dll and (2) changing Microsoft.Web.Extensions to System.Web.Extensions and (3) Microsoft.Web.Extensions.Design to System.Web.Extensions.Design

    Also for WPFEHostExtender website i did above changes but yes i get following error:

    " Could not load type ‘System.Web.Handlers.WebResourceCompressionModule’ from assembly ‘System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’."

  12. PinalBhatt says:

    Yes i could successfully compile and Run  WPFEHostExtender website using ASP.Net AJAX RC1 toolkit after removing lot many lines of code from web.config.

    Following contetnts in Web.config were sufficient to run the xaml clock :

    <?xml version="1.0"?>

    <configuration>

    <system.web>

    <compilation debug="true">

    <assemblies>

    <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

    <add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

    <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>

    </compilation>

    <httpHandlers>

    <add verb="GET" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler" validate="false"/>

    </httpHandlers>

    </system.web>

    </configuration>

  13. .Net Gate says:

    While browsing today about the "WPF/E" i found a nice post that i thought to share with you, it’s from…

  14. First CTP of Windows Presentation Foundation Everywhere (WPF/E) was released last december, Joe Stegman

  15. Delay's Blog says:

    Earlier today I presented the DEV304: ASP.NET AJAX Control Toolkit Unleashed: Creating Rich Client-Side

  16. 对网上的WPF/E文章汇总,前一部分来自思归的WPF/E技术文章,每天整理一些资源.

    1。WPF/E起步–GettingStartedwith

  17. 半山旅客 says:

    新的技术层出不穷啊,微软的任何一个动作都有可能引起程序界的轰动或者骚动。追着微软真累:(

  18. Jacky_xu says:

    摘要

    昨天诸事不顺,早晨起来肠胃开始不舒服。下午坚持写好本篇推荐文章之后,还没发布居然鬼使神差一般就把草稿删除了?!WindowsLiveWriter处理数据安全方面确实有一套,删除的草稿无论用…