I would like to add reporting capabilities to a net application. My data source is the only data model of the application, i.e. a bunch of objects that can be generated or loaded (not necessarily from a database).
Initial Plan A report data from these objects to XML file, and then use XSLT to convert to the Excel report file. The report can then be shown in the application with browser controls.
However, I have found that Microsoft is present. Reporting. * Namespace and what I have tried, it seems that there may be a consideration for my reporting in the classes and control of it, would it be a good idea to use it instead? Will it save work compared to the XML / XSLT approach? Is there a possibility of running the limits of the Microsoft Reporting Framework (if any)?
To consider some things.
1) SQL Server is part of the reporting services, so if you go that route you may have an additional license problem.
2) Reporting services can prepare web pages or can be used in WinForms with complete paging, sorting, all reports, yoga, etc. Etc. - It's really hard in XSL it will play well with the printer.
3) Reporting services come with a WYSIWYG editor to create reports This is not perfect in any way, but it is much easier than hand crafting.
4) Creating XLL to create XLL can be a real demonstration hit. XSL works on a complete XML DOM, and this is probably a big document if you are working with a multipurpose report. I hope the reporting service will work very fast.
5) Reporting services can take full advantage of the net, so you can get many other features for free.
Using the reporting services, taking everyone on board will save you time, until your reporting requirements are very simple. This is less fun.
Comments
Post a Comment