It will be hard. First, you need a ViewState, so you will need to place the report on a regular WebForms page. This is not so bad because WebForms and MVC work side by side.
The hard part is tied to real IEnumerable objects, and not to ObjectDataSources objects with fake balance.
The first step is to create a report data model. You can do this in code, with queries, no matter what you want. A structure similar to this one (but obviously much larger) is typical:
public class ReportSource { public Floogle[] Floogles { get; set; } } public class Floogle { public Doodad[] Doodads { get; set; } public string Text { get; set; } } public class Doodad { public int Number { get; set; } }
The trick is to use the BindingSource control in your report and set the DataSource property to typeof(ReportSource) - yes, the data source is the type of your report model.
When developing a report, you will not get much wealth, but you can do it.
For third-party reporting solutions, we found Telerik to be the best option.
Matt hinze
source share