Some useful .NET reporting components provided by NReco:
- PdfGenerator: can generate PDF by HTML document or URL (wrapper for wkhtmltopdf, FREE)
- PivotData: calculates data for pivot tables and charts; implements in-memory multidimensional array (data cube) and query operations (slide, dice, roll-up). Core library is free; commercial Toolkit provides pivot table rendering and export components, interactive ASP.NET pivot table builder.
The separation of .NET is not bad, still you have to make the arrangement in some structured way - let's say first will be the most used platform/technology - ASP.NET or WinForms or WPF or else, second will be second most used etc. You can see which platform is most used based on some credible source or using your opinion. You can even arrange them by name. Still, if you want to have desktop technologies first, then the web, then mobile, probably you will have three big headers - desktop, web, mobile, and as sub-headers will go each particular technology.
Then, for each .NET technology, you will place Paid/Free libraries, controls, components.
When you enumerate each particular vendor, again you have to decide in which way you will arrange them - first will be the vendor with most sales (based on some credible source), revenue, most likes on company Facebook page, or other criteria, which you believe is suitable for the case. For your article best judgement will be if your or some of your colleagues has a real-hands experience with some vendor and can give non-biased real opinion. But no marketing terms or some company boosted community members count or visitors of some site, managed by vendor itself.
Then, for each particular .NET technology you can place name of the vendor and the name of its product for this technology - DevExpress DXperience, Infragistics NetAdvantage etc, this will make the web search for particular technology much easier and better. Some company can change the name of its product if product has a bad reputation, so I strongly encourage to state the former names of products/toolkit and their current ones.
And finally, do not get offended by the comments or scores. It is good that such article exists, and a comment is just a comment, and a article score is just an article score - it does not mean that the author is a bad person or bad professional, it means that something can/should be improved
Last Visit: 31-Dec-99 18:00 Last Update: 25-Jul-16 16:31