Current filter:
                                You should refresh the page.
                                  • [DevExpress Support Team: CLONED FROM T360117: How to integrate DevExpress reporting components into an ASP.NET Core (a.k.a vNext / ASP.NET 5 / MVC6) web application ]
                                    Hi Vasily,
                                    i've carefully readed all your post regarding report viewer and report designer into mvc core 1.0 app.
                                    I'm a bit confused, let me clarify the question: currently an the ASP.NET backend is required for because .NET Framework server backend is required for the report generation .
                                    I've explored 17.1 project you have enclosed to Eugeny's solution .
                                    I could see two projects all of them are currently using .NET Framework 4.5.2.
                                    What do you mean when you say core web app (without) .NET Framework should be decoupled from the backend core with .net support?
                                    Inspecting 17.1 project i could not find a clean core web app (without .net framework).
                                    For us will be very usefull having separeted backend project encapsulating all the necessary code to access reporting, while the source front-end will be an core 1.0 project without .Net Framework.
                                    Do you mean the DevExpressASPNETCoreReporting project will be the backend and a new core web app will be a front end?
                                    If this is right, could you please complete 17.1 solution adding a clean mvc 1.0 project as front end?
                                    This new project will call DevExpressASPNETCoreReporting in order to process report
                                    Thank you

                                1 Solution

                                Creation Date Importance Sort by

                                Hi Fabio,

                                Note that it is not possible to use the approach demonstrated in the How to integrate DevExpress reporting components into an ASP.NET Core (a.k.a vNext / ASP.NET 5 / MVC6) web application article in ASP.NET Core 1.0 applications (that do not use .NET Framework). That's because our server-side Reporting engine uses theGDI+ (System.Drawing) library's functionality to draw a report's content and export it to certain formats. This assembly is not provided as part of .NET Core, and it is not possible to use this library on Linux and macOS machines.
                                In any case, you can still integrate the client-side part of our reporting components (frontend) to such applications and run the server-side Reporting engine on a separate web server (backend) located on a Windows machine. This approach is described in the DevExtreme Reporting help topics. In these help topics a DevExtreme application is used as a frontend, but you can use any other Web application instead. Let us know if you have any further questions regarding this approach.

                                Show all comments
                                • fabio borghi 08.08.2017

                                  Hi, Vasily
                                  i've followed this two sample because i could not find other documentation:
                                  Currently i've two projects:
                                  - core mvc project (the front end)
                                  - core mvc with .net framework project (the back end)
                                  We are not able to view report on designer and on viewer.
                                  Enclosed you could find the sample solution in order to illustrate our behaviour.

                                  1. Open solution
                                  2. restore nuget packages
                                  3. compile Web.Reports.Library
                                  4. install-package Gulliver.Web.Reports.Library.17.1.5.nupkg on Web.Reports.Api project
                                  5. start both Web.Reports.Api and Web.Site
                                  6. press "report viewer" and "report designer" action link on tool bar
                                  As you could see report vieewer correctly show the viewer but not report content.
                                  Report designer does not show designer and report.
                                  Could you please help me in order to solve this issue?
                                  Thank you


                                • fabio borghi 08.09.2017

                                  Here is second release of our sample; we have fixed a couple of bugs

                                • Vasily (DevExpress Support) 08.09.2017

                                  Hi Fabio,

                                  Thank you for sending us your sample. We need some additional time to research it on our side and determine the exact cause of this problem. We will update this thread once we have any results. Please bear with us.

                                • fabio borghi 08.09.2017

                                  Thank you

                                • Vasily (DevExpress Support) 08.10.2017

                                  Hi Fabio,

                                  We researched the sample project your provided and found several issues that prevent Report Viewer and Report Designer from correct operation in your application. s for the Report Viewer, we found that the "dx-designer.js" script is registered in your "Viewer.cshtml" view for the second time. This file is already registered on your Layout view page, so it is not necessary to register it for the second time here. Also, the backend URL is not completely correct, because your backend Viewer controller's route is set to "DXXRDV". Use the following URL instead:

                                  var backendPrefix = "http://localhost:52731/"; DevExpress.Report.Preview.HandlerUri = backendPrefix + "DXXRDV";

                                  Finally, I would like to remind you that it is necessary to call the client-side OpenReport method after the Viewer's model was initialized to open some report's preview on your web page:


                                  As for the Web Report Designer, I see that its client-side model is not correctly specified for the Report Designer in your "Designer.cshtml" view's code. That's because it is loaded from the view's model, however, no model is passed to this view from your controller. So, the designer's model appears empty. To accomplish your task, use the approach similar to the one demonstrated in the Integration of the Report Designer into a DevExtreme application help topic to load this model from your backend and assign it to your Web Report Designer.

                                  Let us know if you have any further questions regarding this.

                                • fabio borghi 08.10.2017

                                  Hi Vasily,
                                  i've remove double "dx-designer.js" reference
                                  i've set :

                                  DevExpress.Report.Preview.HandlerUri = backendPrefix + "DXXRDV";

                                  As you could see, i've already open the report here in Api project:

                                  public IActionResult Viewer(int Id) { var clientSideModelGenerator = new WebDocumentViewerClientSideModelGenerator(); var clientSideModelSettings = new ClientSideModelSettings { IncludeLocalization = false }; var report = XtraReport.FromFile(@"C:\Temp\XtraReport1.repx", true); return Json(clientSideModelGenerator.GetJsonModelScript(report, "/DXXRDV", clientSideModelSettings)); }

                                  By the way i've also tried to open report as you have suggested, using:


                                  AND FINALLY: nothing to do!
                                  IT DOES NOT WORKS!

                                  Could you please give me back our sample solution with the necessary path in order to do it works?
                                  Could you please give us a link to the documentation on how to do this job?

                                  Thank you for your comprehension

                                • Vasily (DevExpress Support) 08.11.2017

                                  Hi Fabio,

                                  We need some additional time to prepare a modified sample project for you. We will update this thread once we have any results.

                                • fabio borghi 08.11.2017

                                  Thank you very much.

                                • Vasily (DevExpress Support) 08.11.2017

                                  Thank you for your patience, Fabio. We modified your sample project to demonstrate how you can accomplish your task. You can find the modified sample in the attachment.
                                  Note that the suggestions I made in my previous comment were not completely correct, because I missed the fact that the client-side models of our Reporting controls were loaded in your Gulliver.Web.Site project by sending requests to the Report controller in your backend. Please accept my apologies for missing that fact. So, it is not necessary to call the "OpenReport" method for your Report viewer and send an AJAX request to load the Web Report Designer's model.
                                  In any case, we found that the Report controller implementation was not completely correct, so the response sent by this controller was wrapped in a string twice. As a result, the model was represented as a plain string in the client-side code. To resolve this problem, we modified the Report controller's code to make it return plain text instead of a JSON result.
                                  Also, we found that the jQuery UI CSS style sheet was not registered on your Layout view page, and the "win10" theme's stylesheet that is not supported by our Reporting controls was also registered there.

                                • fabio borghi 08.16.2017

                                  Hi Vasily,
                                  thank you for your answer!
                                  I'm triying to complete the task and i'm strictly closed to the final solution.
                                  Just a couple of issues:

                                  1. how could we disable "save as" command on report designer? (we have tried to do not register CustomReportStorageWebExtension clas s; without this class "save as" disappears but the "save" button on report designer does not works)
                                  2. we have set an array of anonymous values on DataSource properties of custom report (resultset is a query maked by our customer without model or class); how could we do not see our three sample records on designer and viewer?
                                  See enclosed modified sample.
                                  Thank you in advance
                                • Vasily (DevExpress Support) 08.16.2017

                                  Hi Fabio,

                                  These issues do not seem to directly relate to your original inquiry. To avoid discussing multiple topics in this thread, I have extracted these issues to separate tickets created on your behalf:

                                  >>1. how could we disable "save as" command on report designer?
                                  T546360: Web Report Designer - How to disable "Save As" command in .NET Core application

                                  >>2. how could we do not see our three sample records on designer and viewer?
                                  T546363: The anonymous values that come from an array are not visible when XtraReport is edited and previewed in .NET Core application

                                  These tickets have been placed in our processing queue and will be answered shortly.

                                • fabio borghi 09.07.2017

                                  Thank you