Share via

Form rendering in the web client

  • Article

To be displayed in the Microsoft Dynamics GP web client, each form in your Visual Studio Tools integration must be rendered as a Silverlight form. There are two techniques that are used to render the .NET form: dynamic rendering and custom rendering. It is the developer's responsibility to indicate which type of rendering a .NET form will use in the web client.

Dynamic rendering

With dynamic rendering, the Microsoft Dynamics GP web client automatically creates and displays a Silverlight form, based on the definition of the .NET form in the Visual Studio Tools integration. For dynamic rendering to work, the .NET form must use controls only from the supported list. The supported controls are:

  • Button
  • CheckBox
  • ComboBox
  • GroupBox
  • Label
  • ListBox
  • RadioButton
  • TextBox

If a Visual Studio Tools integration uses controls that aren't supported, those controls won't be rendered in the Microsoft Dynamics GP web client. Refer to Dynamic Rendering for detailed information using dynamic rendering in your integration.

Custom rendering

You must use custom rendering when your Visual Studio Tools forms contain controls that aren't supported by dynamic rendering. With custom rendering, you are responsible for creating the Silverlight form that displays in the web client. You must also handle the messages that are sent between the Visual Studio Tools add-in (running on the server) and the Silverlight application (running in the web client). Refer to Custom Rendering for detailed information.