Crystal Reports build failed in Visual Studio 2019 Setup project

[former_member4247]

I am using Visual Studio 2019 Version 16.11.7 with .Net version 4.8.04084 and Crystal reports for Visual Studio version 13 Service pack 29.

Whenever I add the CrystalReportViewer (13.0.4 32 bit I think) to my VB application I can run the project in Visual Studio and the report displays.

When I add a SETUP PROJECT to the solution I can build the VB application but when I go to build the setup project I get the error Rebuild ALL FAILED There is no other error message

If I remove the Crystal Report and the References I can build the setup (but of course there is not report)

The report is just a BLANK report, I just want to get the setup project to work with a Crystal report on the VB form.

[former_member11696 · Accepted solution]

That's a question for Microsoft or Google....

Use Google and search for adding MSI packages to your deployment project.

[former_member4247 · Accepted solution]

The process is needlessly complex, like most microsoft "improvements" . I am going to close this out and re-write it in VS 2010. it would be quicker than struggling with the XML bootstrap.

[former_member11696]

See the Platforms info:

SAP Crystal Reports, Developer Version for Microsoft Visual Studio – Supported Platforms

VS 2019 is not supported until SP 25.

Since you are still in development download the latest SP 31:

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

Close all instances of Visual Studio.

Then uninstall ALL MSI packages from your development PC first.

The uninstall the EXE, integration into Visual Studio.

Install SP 31 EXE on your Development PC:

CR for Visual Studio SP31 install package

When it prompts to install the 64 runtime click OK.

Now for distribution download either the 32 bit or 64 bit MSI package, CR runtime is for your app platform and not the OS platform, x86 or x64.

CR for Visual Studio SP31 CR Runtime 32-bit MSI

CR for Visual Studio SP31 CR Runtime 64-bit MSI

Include those in your Distribution project for your application.

See mu blog for upgrading also:

https://blogs.sap.com/2020/10/30/upgrading-a-visual-studio-2008-2019-.net-project-with-the-latest-cr...

DO NOT mix versions, it won't work, it may be could also cause issues.

Don

[former_member4247]

How do I add the CR Runtime engine to my setup project in Visual Studio? When I go to my setup project and click on VIEW then

right click on INSTALL and Add Custom Action it only allows me to add .EXE files, not MSI

Sorry, this is getting VERY fustrating!

[former_member792179]

Is there no way to have the Setup project just install the CR runtime as a prerequisite?
Not that it's that big of a deal, but why on Earth would the CR runtime be available as a prerequisite, but it isn't downloaded while running the Setup on the machines? Why bother with a bootstrapper that does absolutely nothing? (no prompts, no download, nada - unlike all the other prerequisites, that, if not on the PC that my application will be installed to, I get a prompt to install them: for DotNetFramework, extra libraries, etc. Not for CR. Is this a license thing?

[DellSC]

You have to configure your setup to do one of two things:

1. Install a version of the Crystal for VS SDK runtime that matches the version that you're using for development.

2. Don't install the Crystal for VS assemblies. Then manually install the runtime prior to installing your application.

What you cannot do is have the setup copy over just the Crystal for VS assemblies that your application references. The internals of the SDK are based on COM objects which have to be registered in the repository and just copying the files over won't work.

-Dell

[former_member4247]

When I add a Custom Action to the Setup project for CRforVS13SP29_0-10010309.EXE

Visual Studio crashes and closes when I build or rebuild the Setup project.

[DellSC]

CRforVS13SP29_0-10010309.EXE is the integration with Visual Studio - it's NOT the runtime you need when deploying your application. You need to go to the "origin.softwaredownloads.sap.com" link in the Crystal for VS wiki. Set the options like below:

then click on "GO". Sort the results by "File Title" by clicking on the column header. Then scroll down until you find the "SP 29" options. You'll need to select the runtime architecture (32- or 64-bit) based on how you've compiled your application. I would select one of the .msm options for this as "Click Once" can be difficult to configure and get to work correctly.

-Dell