Reportengine.msm, Crnetruntime.msm, Mapping.msm, License.msm,ĬrystalReports10_NET_EmbeddedReporting.msm, CrystalReports10_NET_RemoteReporting.msm, CrystalReports10_NET_WebServiceReporting.msmĬ:\Program Files\Microsoft Visual Studio 8\Crystal Reports\CRRedist\IA64Ĭ:\Program Files\Microsoft Visual Studio 8\Crystal Reports\CRRedist\X64Ĭ:\Program Files\Microsoft Visual Studio 8\sdk\v2.0\Bootstrapper\Packages\Crystal ReportsĬ:\program files\microsoft visual studio 8\sdk\v2.0\bootstrapper\packages\crystal reports However support queries or questions regarding details of deployment should be submitted to the " NET Development - Crystal Reports" forumĭatabase_Access.msm,Database_Access_enu.msm, Managed.msm, Regwiz.msmĬrystal_Database_Access2003.msm, Crystal_Database_Access2003_enu.msm, Crystal_Managed2003.msm, Crystal_regwiz2003.msm Please note any comments are very appreciated.
The following matrix is a summary of runtime information for Crystal Reports from Version 9.1 for VS. XCopy deployments are not supported, nor will they work. It is therefore imperative that all runtime deployments are done by use of the MSM or MSI files. Also, note that the CR.NET component relies on COM Interop for the backend report processing engine. As each version of Crystal Reports has its' own specific runtime which must be correctly deployed, it is critical that the deployed runtime be in agreement with the Crystal Reports assemblies for Visual Studio. I have also added supported Operating System field as well as supported framework for each version of Crystal Reports. In this article, I want to clarify what MSM or MSI files belong to which version of Crystal Reports and which of these will work on VS.
NET, there is some confusion on which Crystal Reports runtime needs to be distributed with which version of Visual Studio. With the increasing number of versions of Crystal Reports and Visual Studio.
0 kommentar(er)
