cool hit counter Crystal Reports 13.x (CrystalReportsforVS2010) installation and deployment experience_Intefrankly

Crystal Reports 13.x (CrystalReportsforVS2010) installation and deployment experience

The last two days have been really bumpy with the installer, one problem after another, first to implement custom actions now chewing vbs, and then the installation process keeps reporting errors:.

Various searches, various attempts, finally got it right, and accumulated some experience to share.

First of all all the CR for VS2010 stuff is here.

A quick note on the resource download table, which is pictured here (dare I say it's all out to SP10, I'm using

Each column represents a category of resources and each row represents a version, and I will only describe the categories of resources that I am aware of.

Install Executable: I understand it to be the full version, which includes everything from the VS plugin, report designer, runtime environment, etc., which you can install to create CR reports in VS. For development machines.

MSI 32/64 Bit: Runtime environment standalone installer for 32/64 platforms respectively. is what is installed on the client's computer, which is what I refer to below by the MSI integration method.

MSM 32 Bit: It is also a runtime environment, but it is used to be combined in the installation package and cannot be installed independently. It looks like only the 32-bit version; I refer to it below by the MSM merge method

What else ClickOnce, WEB XML Dep... What? I've never used it, I don't know.

I. MSM consolidation method

This is the way I first chose to do it, and it's the exact way that keeps getting the above error reported.

Advantages: orthodox packaging method; the size of the resulting installation package is nearly 30M smaller compared to the MSI integration method

Cons: The installation time is not short regardless of whether the system already has CR components or not (my environment is at least 2min+), the light software part of the installation process is actually very fast, which equals most of the installation time is spent deploying CR components

One other thing I'm too lazy to confirm right now is that I'm not sure if that method will uninstall the CR component along with the software uninstall, so I'll try again later when I get a chance.

The official documentation for the method is here.

The kids with good E text should be fine if they follow it, and I'll focus on what I think are the key points.

1, CR's msm file at least only need and a can, is CRRuntime_13_x.msm, more than 40M that, the rest is the language package and a CRRuntime_maps_13_x.msm, maps this do not know what for, anyway, I did not and does not affect the use. Language packs are on demand and are just that.

2, in addition to and 4 VC80 msm, respectively: Microsoft_VC80_ATL_x86.msm, Microsoft_VC80_CRT_x86.msm, Microsoft_VC80_MFC_x86.msm, Microsoft_VC80_MFCLOC_x86.msm. This is reflected in the screenshot in the official article. The key problem is that after installing VS2010, there will only be VC100 version of msm in [C:Program Files (x86)Common FilesMerge Modules], where to get VC80 really made me tossed, and then it was installed in a virtual machine VS2005 to get it, has been uploaded to the network disk:. Just download it and put it in the Merge Modules directory above.

3. Another key is that the client has to install this , the ATL update for the VC++ 2005 SP1 distribution. As an aside, there are these 4 distributions of VC++05 that I know of: VC++05, VC++05 SP1, VC++05 SP1 ATL, and VC++05 SP1 MFC. From experience, SP1 contains RTM, and both ATL updates and MFC updates contain SP1 again, but ATL and MFC should not contain each other (judging by file size). Anyway, for this example, you only need and must install the ATL update on the client, the reason for that error that was always reported before was because the client only had RTM or SP1 installed, which is also mentioned in the official article.

Complete the above 3 points and the MSM method will be fine. To be honest, it's a lot of work to figure out the above key points, and I'm not sure if it's because those authors have good RP and don't have problems or what.

II. MSI integration method

The method is actually based on the principle of installing the CR runtime environment standalone installer (see the resource table description section above, hereinafter referred to as CR MSI, all the installers below refer to the software installer), and then installing the software itself, which has the same effect as installing it separately manually, except that if it is integrated into the installer, the CR MSI is called by the installer to install it, instead of installing it manually. As usual, a few of the advantages and disadvantages as I see them.

Pros: no tossing and turning. As the CR MSI can be installed independently, it has been integrated with VC80 msm, ATL or something, as long as it is installed can already support the report run; the other is that this method can write conditions to determine whether the CR components have been installed, if they have been installed, they are not installed, which can greatly reduce the overall installation time

Cons: The installation package is almost 30M larger than the MSM merge method. The reason is of course that the CR MSI itself is over 70M in size, so much bigger than the 40M CRRuntime_13_x.msm + a single language pack

In addition this method will reflect the CR operating environment in the control panel [Add/Remove Programs] after installation is complete.

Meaning it can be uninstalled independently, this is a pros/cons each way.

To cut to the chase, the exact method of integration varies depending on the packaging software, so it's not good to go into detail. I use Advanced Installer (AI for short), is to add CR MSI in the prerequisites, after adding the AI can intelligently identify and fill in the installation conditions and what not, that is, when the client machine has not yet installed CR MSI, the installation process will execute CR MSI, otherwise not, so that on the machine that has installed CR runtime environment, the whole installation process is fast. That said, both the MSM method and the MSI method take quite a long time to deploy CR components on any machine that doesn't have CR installed, and that's the bad thing about this nifty Crystal Reports update to this version, the earlier versions were quick to install, this one won't take more than a few minutes to install. So it is because of this issue of installation time that I decided to go with the MSI method after I solved the msm method, the reason being that the latter can be judged and can be left out if it has already been installed (e.g. reinstalling software), while the former just takes a while whether it has been installed or not, and I am quite concerned about the installation time anyway.

III. Manual MSI method

This article is completely cobbled together, it is a manual version of the second method above, no technical content, but as an article listing deployment methods, it is indeed one of the methods, and the method can greatly reduce the size of the installation package, save 70M oh pro. If I may ramble, this method requires two files to be thrown at the client during deployment, which are naturally the CR MSI and the software installer, after which the CR MSI is installed first, then the software. If the client has already installed CR, just pass a green, cruelty-free installer without any additives, which is still somewhat pleasant in the days of ADSL soaring, which is the reason this method was written.

Anyway~ After a few days of tossing and turning, this bird bag is finally tied up and the next project begins...

- Man Bi -

1、Its hilarious This year Tangshan people have come here to buy New Years Eve goods
2、Charging like this is dangerous and can steal all the information from your phone in minutes
3、Human society will be controlled by machines and will certainly be in chaos
4、If you dont want to be a hardworking operator and want to sit in the office to program this UG programming content must be learned
5、Surprise Best GAN Ever Appears Super Real AI Fake Photos Connoisseurs Are Buzzing

    已推荐到看一看 和朋友分享想法
    最多200字,当前共 发送