I tried to just stay on RV9 however, one of the reports was erroring and I had javascript issues with the handler page that it inserts.
So, upgrade I did and not without google's help!
- Install on your machine ReportViewer 10
- change the references in your project to point to version 10 of Microsoft.ReportViewer.Common and Microsoft.ReportViewer.WebForms
- If you registered your control, change this tag in your .aspx or control
- <%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0...
I had a report that was cause compile errors (The processing of Parent for the tablix ‘table1’ cannot be performed) with the grouping. I had to take out the "parent" tag and then all was well. Basically old versions glossed over this mishap, but not version 10. For the long explanation of why you need to do this, go here.
">
<GroupExpressions>
<GroupExpression>=Fields!ClientOrderNum.Value</GroupExpression>
</GroupExpressions>
Finally, when you are deploying to a server with IIS7. Make sure that you add the following to your web.config
>
...
" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
...
webServer>
Finally, as it always happends, when you get it onto the production server something else goes wrong. I was getting this error
Compiler Error Message: CS0433: The type 'Microsoft.Reporting.WebForms.ReportDataSource' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.WebForms\8.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.WebForms.dll' and 'c:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.WebForms\9.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.WebForms.dll'
If you add the following to your web.config it tells .net to always direct to the new version
Happy Reporting
No comments:
Post a Comment