I believe that the usual way to deploy Crystal Report with a .NET program is to set it up as a prerequisite in the publishing settings, and then .msi will be packaged with ClickOnce files on network / network / CD / wtv. When the user runs the setup.exe file, he checks to see if Crystal Report is on the client computer. If not, it launches Crystal Report.msi. But this will always require administrator rights.
My question is: is it possible for Crystal Reports DLL package along with other application output assemblies so that an explicit installation is not required? My application uses many many components, including the installation DLL, enough for most of them. Can I do the same with Crystal Report?
If you are set up to do this yourself, you can control the installation of the Crystal Reports runtime to find out what files / entries / registry settings it creates / modifies. Alternatively, you can decompile msi or download and decompile the mst conversion file from Crystal Reports. When you know what he is doing, write something to do it yourself.
, Crystal Reports Visual Studio.NET . Crystal Reports - , , , .NET.
COM-, , DLL, ... , - (Crystal Reports ).
, , Crystal Reports .NET #, .
, : .
.NET.
I am pretty sure that there is a redistributable library package that comes with the final version of Crystal Reports when you buy it (I'm not sure that this package comes with a version of Visual Studio).
I would provide a separate link to the Crystal Redistributable on the installation site and build a check in the ClickOnce application for Crystal files.