I will also point out that I have tried adding a Parameter called "MyCoolParameter" to the very basic ActiveReportsTest.rdlx report, as it seems the easiest thing to look for when evaluating the PageReport object and its children in the debugger to see if the report is actually being loaded correctly from the StringReader.
I confirmed that the parameter does show up (see attached screenshot)
PageReport report;
string localizedReport = GetLocalizedReport(reportFilePath, reportInfo);
using(StringReader reportReader = new StringReader(localizedReport))
{
report = new PageReport(reportReader);
}
return report;
(I have confirmed our GetLocalizedReport() method is returning valid RDLX xml as I have saved the results in a new rdlx file and edited it in the Data Dynamics Reports designer.)
When the "report = new PageReport(reportReader);" call is made, I see this in my Visual Studio "Output" window for Debug:
A first chance exception of type 'System.NullReferenceException’ occurred in GrapeCity.ActiveReports.v7.dll
As mentioned before the "QuickWatch" on report.Report.ReportParameters[0] shows that the MyCoolParameter exists, so I assume the report is being loaded properly in the PageReport constructor.
I don’t know if the NullReferenceException is relevant, but figure it needs mentioning.
The problem still lies in the HttpHandlers ending up dumping a bad <script> tag for the localized Resources for the WebViewer itself:
<script id="lib.jquery-1.7.2.min.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.jquery-1.7.2.min.js.ar7"></script><script id="lib.jquery.layout.min-1.2.0.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.jquery.layout.min-1.2.0.js.ar7"></script><script id="lib.json2.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.json2.js.ar7"></script><script id="lib.knockout-2.1.0.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.knockout-2.1.0.js.ar7"></script><script id="lib.ui.jquery-ui-i18n.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.ui.jquery-ui-i18n.js.ar7"></script><script id="lib.ui.jquery-ui-1.8.16.custom.min.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.ui.jquery-ui-1.8.16.custom.min.js.ar7"></script><script id="lib.jsTree.jquery.jstree.js" type="text/javascript" src="Command=ArResource;ScriptId=lib.jsTree.jquery.jstree.js.ar7"></script><link id="lib.ui.jquery-ui-1.8.16.custom.css" rel="stylesheet" type="text/css" href="Command=ArResource;StylesheetId=lib.ui.jquery-ui-1.8.16.custom.css.ar7"></link><link id="lib.jsTree.themes.classic.style.css" rel="stylesheet" type="text/css" href="Command=ArResource;StylesheetId=lib.jsTree.themes.classic.style.css.ar7"></link><script id="resources-7.1.7470.0-en.js" type="text/javascript" src="Command=ArResource;ScriptId=resources-7.1.7470.0-en.js.ar7"></script><script id="activereports-7.1.7470.0.js" type="text/javascript" src="Command=ArResource;ScriptId=activereports-7.1.7470.0.js.ar7"></script>
The problem script tag is:
<script id="resources-7.1.7470.0-en.js" type="text/javascript" src="Command=ArResource;ScriptId=resources-7.1.7470.0-en.js.ar7"></script>
It should be:
Command=ArResource;ScriptId=resources-7.1.7470.0-en-US.js.ar7
… not …
Command=ArResource;ScriptId=resources-7.1.7470.0-en.js.ar7
Command=ArResource;ScriptId=resources-7.1.7470.0-en-US.js.ar7 will load the appropriate JavaScript if I manually put that in the URL of my browser
In the sample project, when I load the Active Reports RPX report instead of the Data Dynamics RDLX report, I get the en-US version loaded.
I think I have eliminated any problem being with the RDLX file itself, but I’m not sure why the handlers would put something different down on the Resources script tag for RPX vs. RDLX.
Any ideas?
