They are referenced in web.config like this:
<add assembly="CrystalDecisions.CrystalReports.Engine, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
<add assembly="CrystalDecisions.ReportSource, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
<add assembly="CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
<add assembly="CrystalDecisions.Web, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
<add assembly="CrystalDecisions.Windows.Forms, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
<add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>-->
Website was created and maintained on colleague's machine.
I checked it out from source control.
Solution did not build.
Compiler could not resolve Crystal assembly:
CrystalDecisions.ReportAppServer.ClientDoc
Of course, I had to install Crystal Reports assemblies because they don't exists in bin folder.
BTW here is detail explanation where .NET compiler searches for referenced assemblies:
http://stackoverflow.com/questions/981142/dll-in-both-the-bin-and-the-gac-which-one-gets-used
I searched for Crystal assemblies here:
http://scn.sap.com/docs/DOC-7824
Make sure to download "Install executable" from first column.
You can not self-extract it, it will fail.
Right click on EXE and choose extract.
Then start setup.
Crystal will properly register both in GAC and in Visual studio.
Do NOT use MSI packages runtimes!
They will install but you will not be able to reference them. Worst thing is that you can find them in GAC and even copy. Nothing will work. Tried it. Stick to biggest package that integrates into IDE.
http://msdn.microsoft.com/en-us/library/bb398202.aspx
http://scn.sap.com/message/14688220#14688220
This was my problem to a T. Also had that version of CR, and recently upgraded from VS2010 to VS2013. Tried installing the msi from the page we had both found and it didn't work. The "install executable" did. Just wanted to say thanks!
ReplyDelete