We are migrating our class libraries to .NET Standard in preparation for a move of our server and client host applications to .NET Core. One of the objectives we have completed is the removal of our own WCF services since WCF will not be supported in .NET Core. We use an OData service for all data access so we were never able to utilize your Report Server so we instead built our own "Report Tier" on your ReportService which uses WCF. Do you have plans to migrate your ReportService to .NET Core like you are doing for ASP.NET, WPF and Winforms components? Your ReportService is a critical component for use due to the power it offers us to bake our own data access solution and deliver reports to various client experiences. Thanks.
Yes the WCF functionality is not supported by .NET Core. As the Report Service functionality uses WCF we cannot migrate it to .NET Core. In any case, we are researching a capability of providing some alternative functionality. However, to make any plans we need to collect some additional information on why this functionality is required for .NET Core applications. So, would you please answer the following question to allow us to understand your scenario better:• Why do you wish to use a separate shared app (Server) to generate reports? Have you considered generating report documents in your client WPF application? Note that you can connect a report that lives in your WPF application to your OData services directly, and the report will be generated in your WPF application.
• If we replace old WCF functionality with the functionality that uses WebAPI or MVC controllers, will this suit you?
• What application you are going to use as a server-side application after migrating to .NET Core? Is it an ASP.NET Core 3 application?
• Do you wish to connect the WinForms/WPF report's preview components to this server application? Or maybe you just wish to load exported documents (PDF, Excel, etc.) and print these reports?