Licensing agreement appears on client computer

Question

I'm updating a Visual Basic 2003 app to VB/Visual Studio 2008. The app uses a number of Crystal Reports, and I'm using the CR version embedded in VS for those reports (CR not purchased separately). I've set the Setup project to install the CR runtime modules as part of the app installation (checking it as a Prerequisite that needs to be installed in the Setup project's properties).
When the app installation starts on a new computer, I'm getting a license agreement for Crystal Reports Basic for Visual Studio 2008. The license agreement seems to be the same as I would have agreed to when I installed VS 2008 as a developer--it talks about having a license to redistribute CR as long as it's in conjunction with a VS application. But that's not relevant to a user of my application, who doesn't have VS installed on their computer. I didn't have a license agreement like this pop up when my VB/VS 2003 application was installed. Have I set up the installation process incorrectly, or is Business Objects just getting more legalistic? (The irony is that the agreement states that I shouldn't advertise the CR name in conjunction with my software, but the display of the agreement forces everyone to know that CR is used.)

Answer 1

I haven't responded sooner because I was trying out some different scenarios.
I downloaded the file you suggested. When I installed it on a computer that didn't have .Net Framework 3.5, I got the following error message:
Error 1304. Error writing to file: CrystalDecisions.Data.AdoDotNetInterop.dll. Verify that you have access to that directory.
However, after installing the Framework, it ran correctly. I can see the files in Program Files\Business Objects. (I see the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\10.5\Crystal Reports, but there is no cr ent or cr dev.) I did not get a licensing agreement popup during installation.
After installing the CR modules that way, when I run the Setup.exe program that Visual Studio places in the output folder, I continue to get the prompt for the licensing agreement. (This happens whether or not CR is listed as a prerequisite.) However, if I just double-click on the application's .msi installer file, it installs without a message. That's because, though, it's not installing CR.
This may be a clue: I've noticed that if I uncheck both Windows Installer and Crystal Reports as prerequisites, I still get subfolders CrystalReports10_5 and WindowsInstaller3_1 for the Release folder. I wouldn't have expected that.
I tried to start fresh with a completely new project, following the sample steps to create an application with Crystal Reports that are laid out in the online help. Oddly, when I follow those steps (using the Windows Installer deployment instructions), the CR runtime modules aren't installed at all. I noticed that CR wasn't checked as a Prerequisite in the Publish page of the project's properties, but checking didn't make a difference. Changing the Publish Status setting for the CR files in Application Files on the Publish page from Prerequisite (Auto) to Include doesn't make any difference; the CR runtime still isn't part of the package, and doesn't install, so the app crashes when I try to run it. Pre-installing the CR runtime solves the problem, but the point of setting up a deployment project is supposed to be to have all that done automatically.