Recently I compiled a visual basic .net app in visual studio 2005. It required crystal dlls of Version 11.5.3700.0. (I found these dlls to add as a reference to the project in \program files\common\3.5\managed\d
otnet on my machine). Though I had the same version of crystal (CR XI R2A) installed on the target machine, it didn't work, because the only dlls available on that machine were 10.x.x.x, for some reason.
Fortunately I found what I needed on this link: http://scn.sap.com/community/crystal-reports-for-visual-studio/blog/2011/06/07/where-did-all-the-crystal-reports-xi-r1-and-r2-fixes-go
5.msi on the target machine, which put the proper dll version in the Gac. (C:\windows\assembly), as well as creating a 'managed' folder on the target machine.
Before putting on the net_2005.msi, I had installed the wrong version - crredistx86.msi -- on the target machine. So my question is, in the future, how can I match up the .net runtime packages I need with the version of crystal .dll's required by a .net program? I could not find any documentation at all on this, except a little on the link I posted.