FAQ

Check styles of the scheduler container. If the size is defined in percents, make sure that the parent container has the height settings defined as well.

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

html, body{
    margin:0px;
    padding:0px;
    height:100%; /*mandatory*/
    overflow:hidden;
}

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

If scheduler is placed in other container on the page, you can simply set fixed height to a container element:

cshtml:

<div id="dhx-scheduler-container">
  @Html.Raw(Model.Scheduler.Render())
</div>

css:

#dhx-scheduler-container{
   height: 600px
}

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

But the site where you deploy Scheduler may have a different structure of directories and Scheduler will fail to run correctly.

All you need to do is to redefine the paths, as it 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

DHTMLX Scheduler .Net is a server-side wrapper for dhtmlxScheduler, it

• simplifies data binding and allows using .Net code to configure the calendar
• allows initializing the component with the server-side code
• 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 minified and readable versions of JS/CSS sources are still available in the Scheduler .NET.

If your server-side language is ASP.NET, we recommend you to use DHTMLX Scheduler .NET, since the .NET version provides an extra way for data loading, data binding and data saving that works better with ASP.NET Web Forms and ASP.NET MVC frameworks than with JS dhtmlxScheduler. Besides, the .NET version allows configuring most options and behaviors from .NET code (but isn't limited to .NET only, the JS API works the same as for JS version).

There's almost no time lag between the releases of JS edition and .NET edition of the Scheduler control.