Jan Schreuder on .Net

Destroying applications? Interesting..

Pingback from  deploying a project in visual studio 2003

I am deploying a VS 2008 C# application, using Crystal Reports 9. Do I still use the VS 2008 merge modules, or should I use something else???

Is it worth it to convert to CR Basic for VS 2008???

If you are using Crystal Reports for Visual Studio 2008, in order for your application to work when you deploy it, the most simple way to do it is to install on client computer the "Crystal Reports Basic for Visual Studio .NET 2008" msi package - see support.businessobjects.com/.../runtime.asp

After it installs, applications can use CR... very painless, and no need to use the merge modules

Download merge modules for VS2005 link is not working.

The businessobject site redirects mr to

www.businessobjects.com/.../default.asp

Can you please give me the latest link to download merge module for VS2005

I was able to deploy a report in a .NET 2003 project.  There were some issues with the graphic images and since we are upgrading to VS 2008 in a month I went ahead and downloaded VS 2008 eval early.  I ran the redistributable msi on my development web server but I'm getting 'OBJECT REFERENCE NOT SET TO AN INSTANCE OF AN OBJECT' error on the report.  In my 2003 project I had to create a virtual directory that pointed to the Crystal dll's. to resolve this.  I've tried that on my 2008 project but no joy.  I've problaby have named the virtual wrong as I can't find any documentation for 2008.  I found the 2003 documentation here:  boc.sdn.sap.com/.../235   Ideas?

This is how you deploy Crystal to a Web Site with Visual Studio 2008.

1.Install the CRRedist2008_x86.msi on the web server

2.You will also need to copy a directory and its contents from your computer to the root web of any web site that you create Crystal Reports in.  On my computer this directory was located at:  C:\Inetpub\wwwroot\aspnet_client\system_web\2_0_50727\CrystalReportWebFormViewer4  You will need to copy it in the aspnet_client\system_web\2_0_50727 folder of the root web you are installing the Crystal Report application.  See forums.asp.net/.../992330.aspx for additional information - this fixes problems with the Crystal Toolbar.

3. When you create a report within your asp.net application, it will not publish by default.  You need to change the properties on the report.  I haven't experimented a lot with these but changing the Build Action to "Content" and the Copy to Output Directory to either "Copy on Newer" or "Copy always" worked for me.  

4.  I also experienced fewer problems if when I published, I chose to Delete existing files.

The following VB code sample is provided for anyone else who is struggling with passing parameters via a querystring.  This is much simpler than most of the examples that I found on the net.

Imports CrystalDecisions.Shared

Imports CrystalDecisions.CrystalReports.Engine

Partial Public Class myASPNETPAGE

   Inherits System.Web.UI.Page

   Private Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init

       Dim myReport As New TheReportName

       myReport.Load(Server.MapPath("TheReportName.rpt"))

       myReport.SetParameterValue("@Par1", CInt(Request.QueryString("P1")))

       myReport.SetParameterValue("@Par2", Request.QueryString("P2"))

       'Connection Info

       Dim myConnectionInfo As New CrystalDecisions.Shared.ConnectionInfo

       Dim myTableLogOnInfo As New CrystalDecisions.Shared.TableLogOnInfo

       Dim myDatabase = myReport.Database

       Dim myTables = myDatabase.Tables

       Dim myTable As CrystalDecisions.CrystalReports.Engine.Table

       myConnectionInfo.ServerName = "DatabaseServer"

       myConnectionInfo.DatabaseName = "Database"

       myConnectionInfo.UserID = "UserAccount"

       myConnectionInfo.Password = "Password"

       For Each myTable In myTables

           myTableLogOnInfo = myTable.LogOnInfo

           myTableLogOnInfo.ConnectionInfo = myConnectionInfo

           myTable.ApplyLogOnInfo(myTableLogOnInfo)

       Next

       CrystalReportViewer1.ReportSource = myReport

   End Sub

   Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

   End Sub

   Protected Sub CrystalReportViewer1_Init(ByVal sender As Object, ByVal e As EventArgs) Handles CrystalReportViewer1.Init

   End Sub

End Class    

i was able to deploy CR in VS .Net 2003, but also have

got another problem. the export, print, and other CR View toolbar doesn't appear corectly. the condition was:in my form i'm using tab control that have view tabpage and there's a CR view for each tab page...it doesn't happen before i deploy it...why is it possible...ideas???????????