In the past, using Windows Forms, we could add the Player control directly into the Visual Studio toolbox and then drag and drop it onto the form. Windows Forms created the required references for us automatically. But you can also use styles to declare nonvisual properties. For more information on WPF please refer to this link: px As mentioned above, Windows Forms and WPF are two very different architectures that really have nothing in common with each other. WindowsFormsHost. It is this control that enables us to embed our 3DVIA Composer Player inside a WPF application. So, lets get started. Using Visual Studio, start a new WPF Project. Im using version 2012 for this example, however any version from 2008 onwards will be. In 2006 Microsoft released.NET 3.0. Included in this release was a new architecture for building applications named. Windows Presentation Foundation or WPF for short Microsoft Windows Presentation Foundation (WPF) is a user interface (UI) framework for building Windows client applications with immersive and intuitive user experiences. It. In this post I want to address a technological issue related to the use of the relatively old ActiveX technology together with newer technologies provided by Microsoft that do not natively support plugins such as ActiveX controls. Imagine that you have an application dealing with people, such as a contact manager, and that you represent people in code with instances of a Person class. You can create a data template that defines how an instance of a Person is rendered in the UI. Microsofts Silverlight provides functionality that is mostly a subset of WPF to provide embedded web controls comparable to Adobes Flash. There are many benefits to using WPF over Windows Forms below is a subset of the key benefits that I have found while building applications. WPF also fulfills the need for technology and tools that make it natural to separate the UI from the rest of the implementation as much as possible. The WPF system lets developers decouple visual behavior from the underlying program logic and provides a unified API. Drag and drop a button from the toolbox onto the Window surface and place it near the bottom of the window. You can edit the XAML code as follows: Button x:NamebtnClose ContentClose HorizontalAlignmentRight Margin6,6 VerticalAlignmentBottom Width75 ClickbtnClose_Click/ Note: I added the Click event to the.