Current filter:
                                You should refresh the page.
                                  • Description:
                                    I have added the HTML5/JS based component (such as HTML5 Document Viewer, Web Report Designer, Query Builder, etc.) on my web page, but the client-side errors are thrown at runtime and the component is not rendered on the page. Why does this happen and how to fix that?

                                    Answer:
                                    This behavior is caused by the fact that our HTML5/JS based components require additional client-side script files to operate correctly.

                                    The following script libraries are required starting with version 19.1+  (and newer major builds) :

                                    Third-Party Libraries:
                                    jQuery 1.11.3+
                                    jQuery UI 1.11.4+ (should include core, widget, mouse, draggable, resizable, **selectable**modules, both JavaScript and CSS files)
                                    globalize v1.1.1+ (should include message, number, date, **currency**modules and  cldr, cldr.event, cldr.supplemental scripts)
                                    knockout 3.5.0+
                                    - ace.js 1.1.9 (required for the Web Report Designer only, should include ext-language_tools script)
                                    DevExtreme Libraries:
                                    - dx.all.js (should include the dx.common.css stylesheet along with the theme stylesheet: dx.light.css or dx.dark.css)

                                    Note that you can find the list of libraries required for earlier versions at the end of this article.

                                    There are several ways to include these script files in your application:

                                    1. Automatic integration:
                                    Starting with the version 16.2 (and newer major builds) it is possible to register both Third-Party and the DevExtreme libraries automatically by using the "resources" section in the Web.config file:

                                    [XML]
                                    <configuration> <devExpress> ... <resources> <add type="ThirdParty" /> <add type="DevExtreme" /> </resources> </devExpress> </configuration>

                                    In older versions (from 14.1 to 16.1) it was necessary to enable the embedRequiredClientLibraries option for that purpose:

                                    [XML]
                                    <configuration> ... <devExpress> ... <settings ... embedRequiredClientLibraries="true" /> </devExpress> </configuration>

                                    2. Manual integration:
                                    To include both the Third-Party and DevExtreme libraries manually  leave the  "resources" section in the Web.config file empty. Then include the required client-side libraries in the HTML page header section by using <script>  tags. For example, use the following code:

                                    [HTML]
                                    <html> <head> <script src=".../jquery.min.js" type="text/javascript"></script> <link href=".../jquery-ui.css" rel="stylesheet" type="text/css" /> <script src=".../jquery-ui.min.js" type="text/javascript"></script> <script src=".../cldr.js" type="text/javascript"></script> <script src=".../event.js" type="text/javascript"></script> <script src=".../supplemental.js" type="text/javascript"></script> <script src=".../globalize.js" type="text/javascript"></script> <script src=".../currency.js" type="text/javascript"></script> <script src=".../date.js" type="text/javascript"></script> <script src=".../message.js" type="text/javascript"></script> <script src=".../number.js" type="text/javascript"></script> <script src=".../knockout.js" type="text/javascript"></script> <script src=".../ace.js" type="text/javascript"></script> <script src=".../ext-language_tools.js" type="text/javascript"></script> <link href=".../dx.common.css" rel="stylesheet" type="text/css" /> <link href=".../dx.light.css" rel="stylesheet" type="text/css" /> <script src=".../dx.all.js" type="text/javascript"></script> ... </head> ... </html>

                                    Note that the correct paths to these script libraries should be set in the src/href attribute after copying this code to your application.
                                    I have attached a sample project that demonstrates how you can include these libraries manually. You can find it in the attachment section. Also, you can find all the required client-side libraries in the attached sample project.

                                    Finally, register an empty "resources" section in your Web.config file to disable the automatic registration:

                                    [XML]
                                    <configuration> <devExpress> ... <resources> </resources> </devExpress> </configuration>

                                    In older versions (from14.1to 16.1) it was not necessary to perform any modifications to the Web.config file.

                                    3. Mixed integration:
                                    There is an option to register only Third-Party libraries manually and have the DevExtreme libraries registered automatically. To do that, register only the DevExtreme libraries in the "resources" section of your Web.config file:

                                    [XML]
                                    <configuration> <devExpress> ... <resources> <add type="DevExtreme" /> </resources> </devExpress> </configuration>

                                    Important note: It is not possible to register only Third-Party libraries automatically. That's because it will become impossible to manually register DevExtreme libraries in this case (because DevExtreme also requires certain third-party libraries, that should be registered on the page prior to DevExtreme registration).

                                    In older versions (from 14.1 to 16.1) it was necessary to disable the embedRequiredClientLibraries option to cancel automatic Third-Party client-side libraries registration.

                                    Script libraries required for earlier versions of our suite:

                                    14.1 - 14.2:
                                    jQuery 1.11.3+
                                    jQuery UI 1.10.3+ (should include core, widget, mouse, draggable, resizable, **selectable**modules, both JavaScript and CSS files)
                                    globalize v0.1.0 (Newer versions are not supported)
                                    knockout 3.0.0+ (versions 3.5.0 and higher are not supported)

                                    15.1 - 15.2:
                                    jQuery 1.11.3+
                                    jQuery UI 1.10.3+ (should include core, widget, mouse, draggable, resizable, **selectable**modules, both JavaScript and CSS files)
                                    globalize v0.1.0 (Newer versions are not supported)
                                    knockout 3.3.0+ (versions 3.5.0 and higher are not supported)
                                    - ace.js 1.1.9 (required for the Web Report Designer only, should include ext-language_tools script)

                                    16.1:
                                    jQuery 1.11.3+
                                    jQuery UI 1.11.4+ (should include core, widget, mouse, draggable, resizable, **selectable**modules, both JavaScript and CSS files)
                                    globalize v1.x (should include message, number, datecurrency modules and  cldr, cldr.event, cldr.supplemental scripts)
                                    knockout 3.3.0+ (versions 3.5.0 and higher are not supported)
                                    - ace.js 1.1.9 (required for the Web Report Designer only, should include ext-language_tools script)

                                    16.2 - 18.2:
                                    - jQuery 1.11.3+
                                    - jQuery UI 1.11.4+ (should include core, widget, mouse, draggable, resizable, **selectable**modules, both JavaScript and CSS files)
                                    - globalize v1.1.1+ (should include message, number, date, **currency**modules and cldr, cldr.event, cldr.supplemental scripts)
                                    - knockout 3.3.0+ (versions 3.5.0 and higher are not supported)
                                    - ace.js 1.1.9 (required for the Web Report Designer only, should include ext-language_tools script)

                                Show all comments
                                • Randeep Singh 1 06.08.2014

                                  Please note I'm getting "Error: Object doesn't support property or method 'addCultureInfo'" error on Globalize.addCultureInfo.
                                  I'm using patch Globalize v1.0.0-alpha.3 and I can't find this function within.
                                  BTW, am loading following scripts:
                                      <script src="/Scripts/modernizr-2.8.2.js"></script>
                                      <script src="/Scripts/jquery-1.11.1.js"></script>
                                     <script src="/Scripts/jquery-2.1.1.js"></script>
                                     <script src="/Scripts/jquery-ui-1.10.4.js"></script>
                                     <script src="/Scripts/globalize.js"></script>
                                     <script src="/Scripts/globalize.culture.en-US.js"></script>
                                     <script src="/Scripts/knockout-3.1.0.js"></script>

                                • Vasily (DevExpress Support) 06.09.2014

                                  Hi Randeep,

                                  I have extracted your issue to a separate ticket created on your behalf: T116212: ASPxReportDesigner - "Error: Object doesn't support property or method 'addCultureInfo'" error occurs on the client-side when using the latest globalize script version. Your time and cooperation are appreciated. 

                                • WillAutio 06.16.2014

                                  Hi Vasily,
                                  I tried approach 1) and it worked! A couple things sparked my curiosity:

                                  1. you stated: "to make these client-side libraries be included on your page automatically via our HTTP handler module:"
                                  2. I still had some scipts that are older versions than those mentioned in approach 2)
                                  To investigate, I did the following:
                                  3. commented out the "<script src=..." statements in _rootLayout.cshtml (it still worked)
                                  4. deleted and removed from the project the Scripts folder. (it still worked)
                                  That raised a some questions:
                                  5. Where are the required scripts getting loaded? (I searched for ASPxHttpHandlerModule which I expected to do the loading but could not find it.)
                                  6. What is the downside to doing what I have done?
                                  7. With this approach will I always be using the correct scripts?
                                  Thanks!
                                  Will
                                • Vasily (DevExpress Support) 06.16.2014

                                  Hi Will,

                                  All required script files are included in our assembles. So, when the automatic integration mode is enabled, all these scripts are loaded along with our component scripts. So, it is not necessary to include these script files in your project if the automatic integration mode is used. Also, because these scripts are loaded from our assembles - always suitable (correct) versions are loaded. You can look through the ExtensionsFactory.GetScripts Method help topic to see which script files are included in our assembles.
                                  The only downside of the automatic integration mode is when you want to use the newer versions of the scripts than the versions that are included in our assembles. In this case, use the manual integration mode to add the scripts of desired versions.

                                • WillAutio 06.17.2014

                                  Hi Vasily,
                                  Thanks for your detailed explanation.
                                  Regards,
                                  Will

                                • Vasily (DevExpress Support) 06.17.2014

                                  Will, you are welcome!

                                • Justin Wong 04.23.2016

                                  Hi:

                                  I am using v15.2.9 of the MVCe report. As seen in the attached image, I have added all the script references. Yet, when the view loads, I am still getting the error:  0x800a1391 - JavaScript runtime error: 'MVCxClientWebDocumentViewer' is undefined. EmbedRequiredClientLibraries property is set to false in my config file.

                                  Please advise.

                                • Dmitry Tok (DevExpress Support) 04.25.2016

                                  Hello Justin,

                                  I see that you have created a separate thread regarding this issue (JavaScript runtime error: 'MVCxClientWebDocumentViewer' is undefined). Let's continue researching this issue there.

                                  Thanks,
                                  Dmitry

                                • Kundan Kholiya 1 09.01.2016

                                  Hi

                                  We have to implement End-User Web Report Designer in my application so to explore it, I have downloaded T115434_14.1.zip file opened the solution on visual studio 2012

                                  Since we are using devexpress 14.2 version so upgraded it  from devexpress 14.1 version to14.2 and opened the default.aspx to customize the report, added some label and went to menu items to exit this view so that user can view their customization on browser.  but in menu items there is no exit button.  please suggest what should I do to see the customization on browser?

                                • Dmitry Tok (DevExpress Support) 09.02.2016

                                  Hello Kundan,

                                  I have extracted your question into a separate thread so it will be processed in the context of the How to customize the ASPxReportDesigner menu items thread. Let's continue discussing this case there and thanks for your cooperation in advance.

                                  Thanks,
                                  Dmitry

                                0 Solutions

                                Creation Date Importance Sort by