Best Practice for SSRS Data Source in ASP.Net MVC Project

I have an existing ASP.Net MVC project that uses objects / repositories in a separate project. I need to add reporting functions to this project through SSRS, and I am wondering what is the best way to handle it to access data.

Since I have migrator.net and implemented the repository data layer, I feel that using the database directly and creating a db-dependent sql is out of the question. My first thought was to create a web service inside my web project and use it, but it requires me to write new code and maintain a web service that I currently do not need for anything else.

My next thought was to use my data collection and use my existing repositories in code to populate the reports. Is it possible? I am new to this stack and not very good at tools.

How is this usually achieved? In previous Java EE projects, we always used CXF and created a web service for our reporting tools, but I never felt this was the best solution. How is this usually solved in .Net / SSRS?

+5
source share
1 answer

. . , , , .

, , . , , , , ( , SQLCLR ? ?).

SSRS , - . . . , -, web/pdf/doc/xls .., . , , - .

+4

All Articles