Q: Why is Scheduler not displayed on the page?

A: Check styles of the scheduler container. It must have a valid size in pixels or percents. If the size is defined in percents - be sure that the parent container has some height settings as well.

When Scheduler is placed directly in body , you need to have the next css style, to use the percent-based height correctly:

html, body{
	height:100%; /*mandatory*/

Q: Scheduler works in the development environment, but does not work when I deploy to the website?

A: To simplify initialization, Scheduler generates paths to actions and codebase folders automatically, setting by default as:

  • sitename/Scripts/dhtmlxScheduler;
  • sitename/ControllerName/Data;
  • sitename/ControllerName/Save.

But the site where you deploy Scheduler can have another structure of directories and Scheduler will fail to run correctly.

All you need to do is to redefine the paths, like shown in the example below:

var scheduler = new DHXScheduler();
scheduler.Codebase = Url.Content("~/Scripts/dhtmlxScheduler");
scheduler.SaveAction = Url.Action("Save", "ControllerName");
scheduler.DataAction = Url.Action("Data", "ControllerName");

where Url - System.Web.Mvc.UrlHelper

Q: What's the difference between DHTMLX Scheduler .NET and the JavaScript dhtmlxScheduler?

A: DHTMLX Scheduler .Net is a server side wrapper for dhtmlxScheduler, it simplifies data binding and allows using .Net code to configure the calendar. It provides the way to initialize the component with the server side code, and also provides some helpers for loading and saving operations. So basically, it is “dhtmlxScheduler plus .NET wrappers and helpers”.

All functionality provided by the client-side component (dhtmlxScheduler), as well as a minified and readable versions of JS/CSS sources are still available.

comments powered by Disqus