Contains options that allow you to configure the Web Dashboard's back-end.
You can use the Web Dashboard not only as a standalone application. The Web Dashboard allows you to separate the client and server parts. This means you can:
The table below illustrates correlations between server and client. The column headers display platforms you can use as a server, the row headers show available client counterparts.
Client \ Server
ASP.NET HTTP Handlers
ASP.NET Web Forms (UseDashboardConfigurator = false)1
ASP.NET Web Forms (UseDashboardConfigurator = true)
1 It is a default ASPxDashboardControl mode. See Server-Side API Overview to learn more.
2 In this case, the Web Forms Dashboard sends requests only to its own instance.
Use the following properties / methods for a corresponding platform to configure server settings for the client application:
ASP.NET Web Forms
The code samples below show how to configure the client: set the server's url and pass a custom Authorization header.
For MVC or ASP.NET Core back-end, the url is a controller's address:
DashboardControl.BackendOptions.Uri = "http://www.dashboard.server"; DashboardControl.BackendOptions.RequestHttpHeaders.Add("Authorization", "AuthToken123");
For a WebForms control that uses the DashboardConfigurator's instance API, provide the Dashboard HTTP handler's url instead of the controller's address:
DashboardControl.BackendOptions.Uri = "http://www.dashboard.server/DXDD.axd";
You need to set up cross-origin resource sharing (CORS) on your back-end to configure corresponding permissions to access selected resources from a server at a different origin.