Why some official CrystalDecisions DLL runtime libraries are DEBUG and not RELEASE?

[talbot_sk]

unoptimized-libraries.txtCrystalDecisions.ReportAppServer.Controllers.dll	CrystalDecisions.ReportAppServer.Controllers.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.Controllers\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.Controllers.dll	No	No	Cannot find or open the PDB file.		72	13.00.30.3805	4. 2. 2021 20:58	0000018FB1ED0000-0000018FB1EFE000
CrystalDecisions.ReportAppServer.DataDefModel.dll	CrystalDecisions.ReportAppServer.DataDefModel.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.DataDefModel\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.DataDefModel.dll	No	No	Cannot find or open the PDB file.		73	13.00.30.3805	4. 2. 2021 20:57	0000018FB2000000-0000018FB2044000
CrystalDecisions.ReportAppServer.ClientDoc.dll	CrystalDecisions.ReportAppServer.ClientDoc.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.ClientDoc\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.ClientDoc.dll	No	No	Cannot find or open the PDB file.		74	13.00.30.3805	4. 2. 2021 20:58	0000018FB14E0000-0000018FB14F4000
CrystalDecisions.ReportAppServer.CubeDefModel.dll	CrystalDecisions.ReportAppServer.CubeDefModel.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.CubeDefModel\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.CubeDefModel.dll	No	No	Cannot find or open the PDB file.		75	13.00.30.3805	4. 2. 2021 20:57	0000018FB1050000-0000018FB105C000
CrystalDecisions.ReportAppServer.ReportDefModel.dll	CrystalDecisions.ReportAppServer.ReportDefModel.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.ReportDefModel\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.ReportDefModel.dll	No	No	Cannot find or open the PDB file.		76	13.00.30.3805	4. 2. 2021 20:58	0000018FB24D0000-0000018FB252E000
CrystalDecisions.ReportAppServer.CommLayer.dll	CrystalDecisions.ReportAppServer.CommLayer.dll	C:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.ReportAppServer.CommLayer\v4.0_13.0.4000.0__692fbea5521e1304\CrystalDecisions.ReportAppServer.CommLayer.dll	No	No	Cannot find or open the PDB file.		77	13.00.30.3805	4. 2. 2021 20:57	0000018FB10D0000-0000018FB10E0000

[former_member11696 · Accepted solution]

Actually the first report is slow because CR dynamically loads the runtime as required.

Quick work around is to preload a dummy report with the same data driver your main reports use so it preloads them as well.

It's the nature of .NET...

Also do not use No Printer and check on Dissociate in the Page Setup, that way the engine doesn't look over you whole network for the printer it was designed with.

Other option is to not use Last Page, it forces the formatting engine to format each page to find the last page of the report.

Other options is in the Report Properties, be sure to uncheck all Verify options so it doesn't query the DB while loading.

There's a KBA also on how to optimize the reports for exporting...

If we did build them in release mode we would have no debugging ability except to download a debug version... Same as Visuals Studio, they have a debug a release mode for all of their runtime also....

Thanks for the update, if you want to ask them to build Release versions go to our Enhancement Site, if your post gets enough Votes R&D will look into this...

https://www.sap.com/about/customer-involvement/influence-adopt.html

Update - the reasons we use the Debug version is because 20+ years ago when you could use crpe32.dll, main core engine, for developing we included the PDB files so developers could debug their app. We no longer give out the PDB's so they were removed but the build's are still in debug mode to help our Developers and you enable crpe logging and DB logging.

Don