I have problems here. I updated one of our Winforms products from VS2008 to VS2010 about 4 weeks ago. The conversion was great, but we used Crystal Reports, so I had to install VS2010 Crsytal Reports for Visual Studio 2010 Beta 2. It was great and the designer gave me etc. For the crystal. I decided not to convert the reports when the solution opens, so they are still configured for the original version of the crystal.
Then we continued development for 4 weeks, and now I am starting the first deployment of ClickOnce under Vsiaul Studio 2010, and I am having serious problems. ClickOnce application files are installed as having CrystalReports-related modules as prerequisites. I still want the end user to use Crystal Reports for VS2008, rather than the 2010 runtime, which is a ridiculously large and beta version.
When I publish the manifest, we say that the dependency for the crystal is on version 14.0.2000.0 (Crystal VS2010 crystal version), but all the DLL links in the projects are configured to use a specific version and point to 10.5.3700.0 (VS2008 crystal report version). This means that when you try to install from ClickOnce, this does not allow:
"Cannot install or run the application. An application requires Crystal Cecurity.CrystalReports.Engine Version 14.0.2000.0 to be installed in the global build cache (GAC))
I cannot understand why the manifest intends to use this version number, given that all links point to a different version. If I link the VS2010 time crystals, which are beta versions of the ClickOnce deployment, then the client receives a return error message indicating that 10.5.3700.0 is required. If I install 10.5.3700.0 on the client, they will get a working system, but I have to install version 10.5.3700.0 manually, and before that they had to transfer the epic installation of the 2010 runtime environment (14.0.2000.0), which don’t even get used to.
, 10.5.3700.0 , VS2010 .
, .