Skip to Content
0
Jun 08, 2018 at 04:17 PM

ignore legacy CRUFL in .NET runtime

422 Views

We have an app running Crystal Reports for Visual Studio 2017 SP 22, installed on a customer's server. Our problem is that the report document doesn't close, and it seems to be because of a CRUFL for an older version of Crystal. The older Crystal and CRUFL are from another software company's application, that we have no control over.

Is there a way we can make our .NET runtime application ignore that legacy CRUFL.? The legacy CRUFL is installed and registered in the Windows\SysWOW64 folder.