CHAPTER 7 USING CUSTOM .NET CODE WITH REPORTS
Figure 7-15. Setting a breaK point in Your custom assemblYTroubleshooting Your Project
If you modify a custom assembly and rebuild it, you must redeploy it, because the Report Designer looks
for it only in the Report Designer application folder. If you followed our suggestion in the “Debugging
Custom Assemblies” section to change the output path, it should be in the correct location each time
you rebuild it while debugging. If not, you will need to follow the instructions in the “Deploying a
Custom Assembly” section to move it to the Report Designer application folder. Remember, Visual
Studio will not deploy your custom assembly to your SSRS 2012 server machine; you must copy it
manually. Finally, you may want to keep the version of any custom assembly the same value, at least
while you are developing it. Every time you change the version of a custom assembly, the reference to it
must change on the References tab of the Report Properties dialog box, as discussed earlier in this
chapter. Once your reports are in production where you want to keep track of version information, you
can use the GAC, which can hold multiple versions; this means you have to redeploy only those reports
that use the new features of the new version. If you want all the reports to use the new version, you can
set the binding redirect so that all requests for the old assembly are sent to the new assembly. You would
need to modify the report server’s Web.config file and Rsreportserver.config file.
If you are using a custom assembly and the output on your report shows #Error, you likely have
encountered a permissions issue. See the “Deploying a Custom Assembly” section in this chapter for
information on how to properly set up the permissions.