Archives
-
Hosting a Window Form Control in a SharePoint WebPart
Some months ago I posted about Hosting a Windows Form Control in a web page. I explained there how we can run a WinForm control from Internet Explorer by hosting it in a web page using the <object> tag. Now suppose you want to use the same solution in a custom web part that is included in a Sharepoint site. I will describe here where the control library should be placed and how it can be referenced from the web part.
-
CCF HAT - Making use of DDAs from Legacy Adapters
Although Data Driven Adapters (DDAs) are mainly designed for Automation Adapters in HAT, we can make use of them from legacy adapters, too. Here's an example of an external VB application, which is configured to use a legacy application adapter and a WinDataDrivenAdapter with the corresponding bindings:
-
CCF 2008 Hosted Application Toolkit
The Hosted Application Toolkit (HAT) is a new component of CCF 2.6 (2008) that facilitates the task of automating the UI of the hosted applications. It consists of two main parts: the Data Driven Adapters (DDA) and the Automations (WF workflows) that automates the hosted application using the DDAs.
-
Silverlight article published this month
My colleagues Ariel Neisen, Federico GarcĂa, Rodolfo Finochietti and I wrote the cover article of the #42 edition of the .Code Magazine (in Spanish) about Silverlight. The article talks about this new technology's fundamentals, architecture, programming tools, advanced features, code samples and a lot more.
-
Choosing the right WCF binding
A WCF binding is the endpoint component that defines how the client needs to communicate with the service. It groups settings such as underlying transport protocol, security requirements, and message encoding.
-
CCF 2008 New Features
The 3.0 version of the Customer Care Framework (CCF) is out! Among its new features we'll find:
-
Hosting a Windows Form Control in a web page
Although it is not the most common use of it, it is possible to host a Windows Form Control in a Web Page and run it from within Internet Explorer. This allows to build powerful client side functionality with all the advantages of using the .Net framework and executing the control in the client side. Of course there are some restrictions that cannot be left aside. At least the .Net framework must be installed on the client for the control to run. In addition, it is possible that some permission must be granted to the control, too, depending on the actions the control will take on the client machine.
-
WPF Accessibility
Windows Presentation Foundation (WPF) provides a very interesting API for Accessibility called Microsoft UI Automation. It allows programmatic access to most user interface elements on the desktop, addressing the needs of assistive technology products and also for User Interface (UI) tests automation.
The framework provides solutions for both accessibility providers and clients, and it is conformed of four main components (see UI Automation Overview):
- The Provider API (UIAutomationProvider.dll and UIAutomationTypes.dll) defines a set of interfaces that are implemented by UI Automation providers, objects that provide information about UI elements and respond to programmatic input.
- The Client API (UIAutomationClient.dll and UIAutomationTypes.dll) is a set of types for managed code that enables UI Automation client applications to obtain information about the UI and to send input to controls.
- The UI Automation Core (UiAutomationCore.dll) has the underlying code that handles communication between providers and clients.
- The UIAutomationClientsideProviders.dll that has a set of UI Automation providers for standard legacy controls. (WPF controls have native support for UI Automation.) This support is automatically available to client applications.
We will typically use the Provider API to create support for our WPF custom controls, since they don't provide accessibility support by default. We will use the Client API for creating applications that need to communicate with UI elements and eventually automate the use of other program's UI.
-
New @ weblogs
Sole
-
Working around VSTO SE's lack of document-customization for Excel 2007
This post was originally published at http://solepano.blogspot.com
-
Developing a Custom Property Comparison Validator using Entlib's VAP
This post was originally published at http://solepano.blogspot.com
-
Workflow Foundation conference's material
This post was originally published at http://solepano.blogspot.com
-
Sign up in the WF's conference @ MS Argentina
This post was originally published at http://solepano.blogspot.com
-
Environmental Overrides
This post was originally published at http://solepano.blogspot.com
-
How-To: Implement a WCF Authorization Manager Using AzMan
This post was originally published at http://solepano.blogspot.com
-
Documentation Generation in .Net 2.0
This post was originally published at http://solepano.blogspot.com
-
More on WF: Getting Started
This post was originally published at http://solepano.blogspot.com
-
My turn in the blog-tag game!
This post was originally published at http://solepano.blogspot.com