This page is a Draft, its content is not complete and might contain errors.
This article applies to:
- CWR Mobile CRM 1.2/4.0/4.1
- Microsoft Dynamics CRM 3.0/4.0
provides a plug-in architecture for custom controls. A custom control can be written in any
.NET Compact Framework 2.0 compliant language, such as C# or Visual Basic .NET.
A Custom Control is a (visible) control that you can use to modify or augment the default behavior of a form. You could e.g. "override" the behavior of a standard input control. Or you could add a custom control that adds new functionality.
Some examples:
- You could create a custom control that links two existing controls together and adds validation to those controls.
- You could create a custom control that integrates with a route navigation application and uses values from existing controls as input.
- You could create an (invisible) custom control that fills default values when the form loads.
- You could create a custom control that presents another input method for an existing control, thereby overriding that existing control.
- You could create a custom control that represents a "toolbar" from which you can start several actions on the form (e.g. a Resolve Case button).
To build a custom control you need to create a .NET Compact Framework 2.0 control that inherits from
UserControl and implements the interface
CWR.Mobile.Client.Interfaces.ICustomControl. This interface is defined in the assembly CWR.Mobile.Client.Sdk.dll.
{TrackBack}