ReportViewer not finding assembly in webapp Bin folder

Hot Topic

Adding rows to a report table horizontally
Add in for Outlook: How to add menu bars to mail items etc?
Problem with locking documents.
Problem getting IIS Hosted service to accept id and pw
problem After installed vs sp1
Problems SmartDocument 1.1 in new Office B2TR
"Error while loading code module" after installing VS2005 SP1
First Remote Function Call takes too long
Adding a macro to excel using C# in asp.net
insert image

Visual Studio

How To Get Element within a Listview CellTemplate
VSTO2005 Excel- Insert Comment into cell
Technique to reduce the Documented file size!!
Generate C# 2005 project files
Problems performing the practice exercises in MSDN Article
Performance Anomaly: XamlReader.Load vs XamlWriter.Save
Controlling what is installed using Tools.InstallCommunityControls
Creating solution folders which do not appear on disk
Hosted Engine and environment variables in MSBuild
Must "Enable all macros" in Word 2007 to run VSTO 2005 document?

ReportViewer not finding assembly in webapp Bin folder

We are experiencing a major problem while trying to call custom code from our report in a web app.

The following message describes our problem: "Unfortunately, because of a bug, copying custom assemblies to the webapp bin folder will not work. We are [microsoft is] hoping to fix this in a service pack. Until then you have to deploy custom assemblies to the GAC." (Rajeev Karunakaran - nov 2005)

But, we are not allowed to add our assembly to the GAC. This means we can not use the custom code at the moment.

Is there a known workaround this report viewer bug Or maybe some hotfix

Thanks in advance,

Erwin Molendyk

Answer this question

ReportViewer not finding assembly in webapp Bin folder

  • Marc Jones

    so how about splitting your c# assembly so that the BL is where it currently is, and putting the reportviewer "Custom Assembly" code into another assembly which you put in the GAC would that work

  • tackett

    Thanks for your creativity :)   But...

    Basicaly, we are looking for a solution which does not involve de GAC.

    This is because using the GAC changes the way End Users, Testers and Programmers work. Unfortunately I've not been able to find any other way. So it looks like we will have to change the development+deployment procedures and train people to use the GAC.

     

  • Will Merydith

    Port your code to VB.NET ( if not already so ) and put it in the "Code" tab of the "Report Properties" dialog.

    NOTE: In the designer view right click in the area outside the form and select "properties" from the context menu.

    Then replace all your calls from the report elemets to directly Code.<funcName>. ( eg Code.GetMyName() )

    You would have a hard time maintaining it if your assembly is large, but thats the only way I can think of without having to use an external assembly.

    Hope it helps

    mqs

  • Chaman Zinga

    Does anyone know if this issue has been fixed in the VS 2005 SP1 Beta

    Kind regards,

    Erwin

  • Brain_Dead_Mind

    Thank you for your reply. Unfortunatly the suggestion is not going to work for us. We need to call our businesslayer (BL) which consists of a large amount of c# code contained in a strongly named assembly.

    For now I am still searching/hoping for a ReportViewer version with this specific bug fixed... One would think that it is common to call your BL from a Report without the need to register it in the GAC.
  • ReportViewer not finding assembly in webapp Bin folder
Answer this question