Search code examples
deploymentcrystal-reportsclickonce

ClickOnce deployment with Crystal Reports prerequisite


I have a .NET Winforms app (created in VS2005) that I deploy using ClickOnce. On one of the forms I have a Crystal Reports viewer control for the user to view the reports, but in order to use that in the app I have to include the the Crystal Reports XI Release 2 prereq which they install prior to installing the app. This basically installs a watered down version of Crystal onto the users machine.

It works publishing this way, but it is sort of a hassle for the user to have to wait on Crystal to install and is a huge hassle for me because publishing the app with the prereq takes a long time to finish because it has to upload the large prereq up to the server.

Since the publish takes so long and new installs are not super common I generally don't include the prereq when I publish changes and instead only publish it with the prereq if a new install is needed.

If you've used ClickOnce to publish an app with Crystal Reports, is this how you've published it or is there an easier/better way.

Is there a way to include/GAC the CR dll's needed instead of including and installing the Crystal Report prereq or is there a way that I can configure the OneClick deployment to not have to copy the file up every time. If I could configure the ClickOnce deployment so that I don't have to include the prereq and instead just point the install to a standard location that would help.

Hope this was somewhat clear and that someone can help out. Thanks


Solution

  • From the responses, it seems that this is pretty common so I'll just post what I do to get around the issue for now.

    First I'll start that I think Bronumski's response should work, but I've not had success with it in the past when I tried it.

    The way that I get around this issue is just to publish the files using ClickOnce to a folder locally and then ftp the files over manually excluding the crystalreport install directory that is created.

    I know this is not a good answer for this, but I don't have to deploy very often anymore and so this is my work around to the issue for now. Please read through all of the other answers to find one that might help resolve your issue.

    Hope it helps. Thanks