次の方法で共有

Where do I deploy my custom assemblies when working with SQL Reporting Services 2005?

  • [アーティクル]

There is a change from 2000 here, and it's not documented in Book Online yet. To further confuse matters, in some earlier builds of Yukon\Whidbey you'll actually find multiple copies of RSReportDesigner.Config on your disk, so you can't always key on it's location.

On the report server, copy the file to the \Reporting Services\ReportServer\bin folder, just like you always have. You still use \Reporting Services\ReportManager\Bin, too.

On the client where you design your report, the best idea is to search for Microsoft.ReportingServices.Designer.dll. You'll probably land in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies. Your custom assembly and RSReportDesigner.Config file should live with the designer assembly, and you can ignore other instances of RSReportDesigner.Config you might find elsewhere (like in C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE)

Comments

  • Anonymous
    August 31, 2005
    And where to deploy/register a custom control when it's used into a report running in LOCAL MODE?
  • Anonymous
    August 31, 2005
    Russell,
    Just FYI, I think <a href="http://neodynamic.blogspot.com/2005/08/barcode-in-reporting-services-2005.html">I found it</a>
  • Anonymous
    September 08, 2005
    The comment has been removed
  • Anonymous
    November 28, 2005
    Hi, further to the original question of where to deploy assemblies when in LOCAL MODE, is the only solution to sign and deploy them to the GAC?

    Is there no simpler way of referencing a custom assembly from an RDLC without requiring the above process?

    Thanks...
  • Anonymous
    November 29, 2005
    I have been told you can drop the assembly in your bin folder, but I haven't tried it myself. Regardless of where you drop it, you'll need to use AddTrustedCodeModuleInCurrentAppDomain(), etc.