Reputation: 1322
I am refactoring an old program to use VS2008 (instead of VS2005) and the 2003 Crystal Reports merge modules no longer work on the client machine.
I am using the CR version bundled with VS2008. Neither the CR10 merge modules downloaded from the SAP site work, nor the CR x86 msi.
Could not load file or assembly 'CrystalDecisions.Windows.Forms, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
I have googled this error to death, and can only find please for help with this exact error...
Upvotes: 2
Views: 38913
Reputation: 1
Just add a forms and link it to a new crystalreportviewer, that way you will see the error disappear.
Upvotes: 0
Reputation: 31
I downloaded the DLLs from here then referenced to their location and the problem was solved.
Upvotes: 3
Reputation: 1322
I've been able to figure it out... finally. (CR experts...please correct me if I've missed details or gotten them wrong)
The fact that Business Objects was purchased by SAP in 2007 was a major roadblock to the answer. The vast majority of forum links point to the old Business Objects website, and are no longer available (SAP has decided to unhelpfully point 90% of these to their home page). This vastly reduced the helpfulness of such posts.
The first source of my confusion was that the version of Crystal Reports that I was dealing with was Crystal Reports BASIC 2008. This is the version bundled with Visual Studio 2008. Versions 11 and 12 are standalone and were NOT what I was looking for.
I had tried using MSMs (packaged DLLs) and msi (runtime installer) for Crystal Reports 2008 (the standalone version) and this is why it didn't work. I had also tried bundling "Crystal Reports" with the installation by using Prerequisites in my setup program. No luck.
So that was my ordeal. Hopefully this helps someone else!
Upvotes: 1
Reputation: 12538
Your application is clearly keeping references to the CR10 version of Crystal - you need to update these to the newer versions. You can do this by double-clicking on My Project, selecting References, removing the existing Crystal ones (which probably say version 10.2.3600.0 next to them) and replacing them with the matching 11.5 versions. I suggest adding the new ones first, then removing the old ones - that way you can keep track. As long as the functionality you're using hasn't been removed from the newer version (which is unlikely), it'll work fine. After that, you'll be able to use the merge modules included with VS2008 to deploy Crystal.
Upvotes: 1