Freigeben über

Important News for .NET Framework 3.5 Beta 2 Developers Building Visual Add-Ins with WPF

  • Artikel

If you are using .NET Framework 3.5 Beta 2 to create WPF applications that support visual add-ins, you should be aware that, in the forthcoming .NET Framework 3.5 RTM, the naming of both the System.AddIn.Pipeline.VisualAdapters class and its members have changed from this [1] to this [2].

Consequently, you’ll need to change your code to use the new type and member names for .NET Framework 3.5/Visual Studio 2008 RTM.

[1] .NET Framework 3.5 Beta 2.0
namespace System.AddIn.Pipeline

{

public static class VisualAdapters

{

public static INativeHandleContract ViewToContractAdapter(Visual);

public static FrameworkElement ContractToViewAdapter(INativeHandleContract);

}

}

[2] .NET Framework 3.5 RTM
namespace System.AddIn.Pipeline

{

public static class FrameworkElementAdapters

{

public static INativeHandleContract ViewToContractAdapter(FrameworkElement);

public static FrameworkElement ContractToViewAdapter(INativeHandleContract);

}

}

Comments

  • Anonymous
    November 09, 2007
    You’re unlikely to be reading this if you haven’t used the .NET Framework to build managed applications

  • Anonymous
    June 10, 2010
    This all works pretty well if one is working with a single FrameworkElement, but how does one handle the case were the AddIn need to return a ResourceDictionary? Thanks