Crystal Reports: Difference between adding a reference to Assembly and adding dll's
Posted on 2009-04-18
This issue is a bit convoluted but i will try to explain. It took me 2 seconds to get crystal reports up running and able to be called from my app on my development box. When i moved to production, it took a while to get it working. Finally we resorted to installed VS2005 on the box and then it worked. Recently, I reinstalled the OS on my dev box to a 64 bit system. Suddenly crystal wasn't working. I was getting this error on any page in my app that referenced it:
Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Normally, with Crystal it would have taken hours to figure this out. But lo and behold, I just deleted the dll's from the bin folder and added a reference (via right clicking on the solution name ) to all the cyrstal 10.5 GAC assemblies. Great...my app works again on my development box.
so here's the problem....Can i just rebuild my site and move the entire thing up to production and it will work? I'm kind of thinking it isn't going to. And I really don't want one version up on the production box that uses dll while my local copy uses references.