# Why do we use eWorld.UI and not the built-in .NET calendar control?

**URL:** <https://discuss.workflowgen.com/t/why-do-we-use-eworld-ui-and-not-the-built-in-net-calendar-control/145>\
**Category:** Visual Studio Web Forms\
**Created:** [October 12, 2006, 12:52am UTC](https://discuss.workflowgen.com/t/why-do-we-use-eworld-ui-and-not-the-built-in-net-calendar-control/145 "2006-10-12T00:52:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [October 12, 2006, 12:52am UTC](https://discuss.workflowgen.com/t/why-do-we-use-eworld-ui-and-not-the-built-in-net-calendar-control/145/1 "2006-10-12T00:52:01Z")

</div>

The eWorld.UI calendar control is used because it uses client side JavaScript and does not cause any postback, so it is more efficient than then .NET calendar control, which does postback. eWorld.UI is free.