ReportViewer, Report Toolbar, Toolbar Image Button is undefined from Visual Studio 2010 to Visual Studio 2013

[Nicola Tramarin]

After migration from VS 2010 to VS 2013, my report return javascript error. The installed version is telerik reporting Q1 2012.

SCRIPT5009: 'ToolbarImageButton' is undefined

ReportInterventi.aspx, line 591 character 13
SCRIPT5009: 'ToolbarImageButton' is undefined

ReportInterventi.aspx, line 603 character 13
SCRIPT5009: 'ReportToolbar' is undefined

ReportInterventi.aspx, line 608 character 10

SCRIPT5009: 'ReportViewer' is undefined

ReportInterventi.aspx, line 631 character 7

Does anyone have suggestions?
Thanks for the help
Monic

[Stef]

Hi Monic,

Please, check if the Browser Link feature of Visual Studio 2013 is turned off, and verify all settings listed in the 'ReportViewer' is undefined javascript error KB article are applied.

In addition, Telerik Reporting has support for Visual Studio 2013 as of Q3 2013.
Thus our recommendation is to upgrade your project to the latest available version. Keep in mind that as of Q2 2013, Telerik Reporting is built against .NET4, which requires all projects to target .NET4+ Full Profile framework version.

Regards,
Stef
Telerik

 

 

[Nicola Tramarin]

I'm sorry, I got confused with sharepoint 2013.
Using VS 2012. However, continuation with the installation of  Q2 2013?
Thanks
Monic

[Nasko]

Hello Enrico,

We haven't encountered the described issue before. In case the 'ReportViewer' is undefined javascript error KB article does not help, please open a new support ticket and send us a runnable sample project exhibiting the issue, so we can review it locally and advise further.

Regards,
Nasko
Telerik

 

 

[LeRoy]

I am also having the problem, transition from version 10.1.16.504 to 10.1.16.615

[Stef]

Hi LeRoy,

In case the question is related to your support ticket #1051947, below is a quote from my response for anyone interested.

"The VS Report Designer is available if the machine has Telerik Reporting installed on it - Installing Telerik Reporting. Then you can import TRDX files in Visual Studio, and vice versa - Import Wizard.
In older versions the report can be deserialized in code.

Note that report created in Visual Studio can be customized as they are classes inheriting Telerik.Reporting.Report. Yet modifications like additional properties, events cannot be serialized for usage in the Standalone Designer.

..........

Instead of printing the report directly, test exporting in PDF file and check the rendered document. Then test to print from PDF Reader and look at the Print dialog settings - if the document is shrunk by the PDF Reader, if the selected printer has settings for rotating or shrinking documents."


Please let us continue the discussion n one of both threads in order to keep a better track on the exchanged information.

Regards,
Stef
Telerik by Progress