Ignore all the warnings about how your web project is dependent on various Crystal Report assemblies since Azure will have them just as soon as your installation file runs.It took me an hour to deploy on my home connection! It will take much longer to upload than usual because you are now uploading an extra 77MB of installation files. Don't be alarmed with how long it takes to deploy.rpt Crystal Report files are set to Build Action: Content and Copy to Output Directory: Copy always. I will share them with you in case you do too in no particular order.
I ran into a few bits and bobs which caused me unnecessary pain along the seemingly clean process outlined above. You are now instructing each instance that starts up with your package to run the Crystal Reports msi file that installs the runtime on the instance ready for its use in Azure. Now in your ServiceDefinition.csdef make this cmd file a start up task by adding the following lines: Set the properties of StartUp.cmd to 'Build Action' = 'None' and 'Copy to Output Directory' = 'Always Copy'. Msiexec.exe /I "CRRuntime_64bit_13_0_2.msi" /qnĮCHO "Completed CrystalReports Installation" > log.txt In that file write the following: offĮCHO "Starting CrystalReports Installation" > log.txt Create a new text file, call it StartUp.cmd and then save it in the root of your web project (next to the msi). Next you will create a command file to execute this msi file. Right click it in the Solution Explorer and set its 'Build Action' to 'None' and also set its 'Copy to Output Directory' to 'Always Copy'. In your web application in Visual Studio you should paste this msi file at the route of your web project and include it in the project. This should extract as a msi file called CRRuntime_64bit_13_0_2.msi.
Crystal reports runtime 13.0.3 download#
Here are the steps you will need to take:įirst of all you will need to download the SAP Crystal Reports runtime engine for.
Crystal reports runtime 13.0.3 how to#
How to install Crystal Reports on your Azure web roleįortunately it is still easy with Azure. With Azure, though, if you remote into the machine and install it, it will work fine until your deployment is redistributed to another machine which it will do at some point due to the nature of cloud computing. This isn't a problem with regular hosting since you can just install Crystal Reports on each of your servers and off you go. The problem is that you need to install the Crystal Reports runtime. If you try to run a Crystal Report in your ASP.NET site without the Crystal Reports runtime installed you will receive a "" with description "The Report Application Server failed". Here is a step by step guide on how to make an ASP.NET project that uses Crystal Reports run successfully on Azure.
0 kommentar(er)
