How do I know which version of crystal .net runtime files to include when distributing an application?

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\dotnet 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 and ran
crystalreports11_5_net_2005.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.
OutOnALimbAlwaysAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mlmccCommented:
To add to the link provided by Ido, the version you need to install depends on the version used to compile the runtime.

The version used in the application should match the version and SP level you are developing the reports with.  This is particularly true for reports developed in the standalone versions.

SAP/Crystal dropped the SDK with CR 2011.  SO to use CR2011 or CR2013 reports you need to develop the application in VS and use the CR for VS .Net that is available from SAP/Crystal.  Again you have to pay attention to the SP level.  I believe SP9 is required for CR2013.

mlmcc
0
OutOnALimbAlwaysAuthor Commented:
Perfect. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.