microsofts bundling of crystal reports dates to visual basic 3 and since then many developers have come to rely on it to build reporting solutions. early on some developers found the programming api too complicated and there were the typical deployment problems that happen with any product that has many versions and upgrades. there have been many improvements over the years to address developer concerns, but when business objects acquired crystal decisions a little over a year ago crystal reports was revitalized. developers will see these benefits in crystal reports xi and the upcoming release of visual studio 2005 (still in beta).
im going to focus on how crystal reports xi affects developers and how it can improve reporting applications. the features that i feel are most important to .net developers are web reporting, dynamic cascading prompting, faster data connectivity, dynamic image location, easier deployment and improved export functionality.
the overarching change in the product is that tasks that used to take a lot of coding are now built in. for example, the following line of code is all you need to add a report to an asp.net page and have the user preview it:
<cr:crystalreportviewer id="crystalreportviewer1" runat="server" width="350px" height="50px"
reportsource=<%# "c:\inetpub\wwwroot\ samplereport.rpt" %>/>adding reports to your application used to mean writing a lot of integration code. the sample above indicates how much... 下一页