Implementing 'Using' with reports+webviewer causes evaluation notice to appear

Implementing 'Using' with reports+webviewer causes evaluation notice to appear

Posted by: david.thompson on 15 May 2018, 1:52 am EST

• 

  david.thompson

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 15 May 2018, 1:52 am EST

  As the title suggests, implementing the following code with a webviewer (viewertype = htmlviewer) with the following code pattern causes the evaluation message to appear.

  I can get the message to disappear by declaring the PageReport variable without ‘using’, I was trying this approach to cope with a separate memory issue (unsuccessfully). This isn’t an urgent issue for me as I probably won’t end up using this code in the future but I thought I’d share here in case anyone else ran into this problem

  
          Using rdlReport As New PageReport()
              Try
  
                  setReportMarkup(rdlReport, "pt", "portrait")
                  rdlReport.Report.DataSources.Add(myDataSource())
                  rdlReport.Report.DataSets.Add(myDataSet())
                  rdlReport.Document.Printer.PrinterName = String.Empty
                  rdlReport.Run()
                  WebViewer.RenderMode = GrapeCity.ActiveReports.Web.RenderMode.Paginated
                  WebViewer.ViewerType = Web.ViewerType.HtmlViewer
                  WebViewer.SlidingExpirationInterval = New TimeSpan(0, 0, 30)
                  WebViewer.Report = rdlReport
  
  
  
              Catch ex As Exception
                  Dim x As String = ""
  
  
              End Try
          End Using
  
  

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 15 May 2018, 10:34 pm EST

  Hello,

  Thanks for the information.

  I am able to replicate the problem at our end. I have escalated this to the development team(Tracking ID 258342) and will revert you back once have any information from them.

  Thanks
  
  Mohit

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 15 May 2018, 10:43 pm EST

  Hello,

  It is “by design”. With such code the license validation is disposed with PageReport object and the rendering engine treats the PageDocument’s instance, used in rendering, as unlicensed.

  Thanks,
  
  Mohit