I am unable to debug a project which uses Crystal Reports 2010. The same project, on the same machine, works flawlessly when installed or run directly from the "bin" folder of the Windows Application.
The application does not fail in the traditional nature of throwing an exception but dies with an actual "hard crash".
I have managed to trace the offending piece of code down to the following statement:
rd = new ReportDocument(); rd.Load(reportWithPath);
Yes, the document exists and all libraries referenced do in fact exist. The path's referenced are accessible. The failure occurs in the load of the document, not the creation of the document object or the viewer object either.
While I do not know why I cannot debug this project anymore, here is what has changed:
- The project was previously targeted at X86 client base. The requirements have been altered for either X86 or X64 clients. Thus the project was set to "Any CPU".
- All references were removed and recreated using the correct 13.0.2000.0 flavored libraries.
- The development box now has Crystal 2010 and the run-times for 32 and 64 bit loaded.
- The development box is a X64 system running 12 GB of memory.
Again, the problem I am having is one of debugging and not experienced by the end users. Using Administrative mode or normal credentials makes no difference.
Do I have a Visual Studio problem or a Crystal Reports problem? Any ideas??