What do we need, to install CR for VS 2010?

[Former Member]

We've got some new developer machines, which we're configuring now.  We use Visual Studio 2010 Premium, and need to use Crystal Reports for VS 2010.  My colleague has done a search, from within VS 2010 on her new machine, which directed her to a page on the SAP website, with several options for downloading such as: Crystal Reports for VS 2010 32-bit, Crystal Reports for VS 2010 64-bit, Crystal Reports for VS 2010 ClickOnce 32-bit, Crystal Reports for VS 2010 ClieckOnce 64-bit, and other things like Crystal Reports for VS 2010 SP4, etc.  We're confused with all of the possible options and aren't sure which we'll need.  We will be using ClickOnce, and we do have clients which are both 32-bit and 64-bit Windows (XP and Win7).  I suppose we may also do installations using something other than ClickOnce.

So, bottom line, which download(s) do we get?

[former_member183750 · Accepted solution]

Hello Rod:

I wrote the following Doc re. just this scenario:

http://scn.sap.com/docs/DOC-7824

To install CRVS2010 you need the "Install Executable" referenced in the above doc. If you will be creating web apps, don't use Service Pack 4, stock with Service Pack 3 (SP4 has web viewer issues). At the end of the install, you will get asked if you want to install the 64 bit files as well (if you're on a 64 bit OS). Other than that, the rest of the files are used for CR runtime distribution (MSM, MSI, ClickOnce).

Hope this helps a bit,

- Ludek

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Share Your Knowledge in SCN Topic Spaces

[Former Member · Accepted solution]

The page you linked to in your reply is the one that we're confused about.  There are 6 columns and 5 rows in that grid.  Do you mean we're to download the support pack, under the collumn labeled "Install Executable"?  Will that put everything onto our PCs for doing development?  My colleague downloaded and installed the 32 & 64 versions under "MSI 32 BIT" and 'MSI 64 BIT", but can't edit the .rpt files in VS 2010.

[former_member183750 · Accepted solution]

Like I said in my first post:

1) To install CRVS2010 you need the "Install Executable"

2) the rest of the files are used for CR runtime distribution (MSM, MSI, ClickOnce).

Runtime distributables will not do anything for you if you want to get VS2010 integration. "Install Executable" wil.

- Ludek

[former_member188030 · Accepted solution]

To Prepare the Development environment

- Install Visual STudio 2010

- Install Crystal Reports for Visual Studio 2010 Install Executable

This will give you a bundled CR designer inside VS IDE and wiil install the CR and InPRoc RAS .NET SDK on your machine.

You can now start developing your CR .NET apps.

For deployment you can make use of the runtimes i.e. either MSM, MSI, OR ClickOnce.

For more on Deployment see the Deployment section in CR for VS 2010 .NET SDK Developer guide.

Search through forums for more information (top right corner search box, of this page).

Also, see the wiki

Getting started and moving ahead with Crystal Reports .NET applications.

- Bhushan

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Getting started and moving ahead with Crystal Reports .NET applications.

[Former Member · Accepted solution]

Thank you, Ludek, I see that we need to install the Install Executable to get CR working within VS 2010.  However, when we go to deploy it we'll need either the MSM, MSI or ClickOnce installs. 

[Former Member · Accepted solution]

Thank you, Bhushan, for your reply.  Now I see we need the Install Executable for doing CR development in VS 2010.  And we'll also need either the MSM, MSI or ClickOnce installs for deploying to our users.

How about the 32-bit vs 64-bit issue?  Do we need to download and install each, if we're going to deploy to each?  I suppose we do.

[former_member188030 · Accepted solution]

Depends, really...

There are no 64 bit MSMs (merge modules).

If you are intend to use MSI, then for 32 bit deployment make sure that he application targets X86 platform and use 32 bit MSI on the server.

And for 64 bit deployment target the app to X 64 and use 64 bit MSI.

Search the forums, a lot of info is available.

- Bhushan