Run Visual Studio 2013 solution with Crystal Reports

[#1]

I have an MVC application originally developed in VS2010. We have Crystal Reports (CR) integrated into it and all works smoothly.

Now, I need to setup some new workstations which will have only VS2013. I can run the site in VS2013, but only because I have VS2010 and previously installed the CR run time files. The new stations won't have VS2010 installed and the SAP installer will not run unless VS2010 is on the machine. This will not be fixed until early 2014 at the earliest (or so I understand).

The new workstations don't need to be able to modify the reports, so I don't care if the full CR application is installed, I just need it to be able to reference the run time files so they can debug other areas of the application.

I cannot remove CR from the application at this time, and cannot install VS2010 on all the new workstations first.

I have tried putting the dlls in the bin folder of the site. I have tried putting them inC:/Windows/Microsoft.NET/ Framework/v4.0.30319/Temporary ASP.NET Files/root/dec0de27/fa4bed84/

Nothing seems to work.

Where do I place the dlls so VS2013 can use them? I know there has to be some way to do this because my workstation can run the site in VS2013 even though SAP hasn't released a 2013 version.

Here is the error when they try to run the application

Server Error in '/' Application.

---

Could not load file or assembly 'CrystalDecisions.ReportAppServer.ClientDoc' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack

trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: Could not load file or
assembly 'CrystalDecisions.ReportAppServer.ClientDoc' or one of its dependencies. An attempt was made to load a
program with an incorrect format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the

assembly 'CrystalDecisions.ReportAppServer.ClientDoc' could not be loaded.

=== Pre-bind state information ===

LOG: DisplayName = CrystalDecisions.ReportAppServer.ClientDoc

(Partial)

WRN: Partial binding information was supplied for an assembly:

WRN: Assembly Name: CrystalDecisions.ReportAppServer.ClientDoc | Domain ID: 2

WRN: A partial bind occurs when only part of the assembly display name is provided.

WRN: This might result in the binder loading an incorrect assembly.

WRN: It is recommended to provide a fully specified textual identity for the assembly,

WRN: that consists of the simple name, version, culture, and public key token.

WRN: See whitepaper http://go.microsoft.com/fwlink/?LinkId=109270 for more information and common solutions to this issue.

LOG: Appbase = file:///C:/Users/Office/Documents/GIT/Site/site/

LOG: Initial PrivatePath = C:\Users\Office\Documents\GIT\Site\site\bin

Calling assembly : (Unknown).

===

LOG: This bind starts in default load context.

LOG: Using application configuration file: C:\Users\Office\Documents\GIT\Site\site\web.config

LOG: Using host configuration file: C:\Users\Office\Documents\IISExpress\config\aspnet.config

LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/Temporary ASP.NET Files/root/dec0de27/fa4bed84/CrystalDecisions.ReportAppServer.ClientDoc.DLL.

LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/Temporary ASP.NET Files/root/dec0de27/fa4bed84/CrystalDecisions.ReportAppServer.ClientDoc/CrystalDecisions.ReportAppServer.ClientDoc.DLL.

LOG: Attempting download of new URL file:///C:/Users/Office/Documents/GIT/ManExAloha/site/bin/CrystalDecisions.ReportAppServer.ClientDoc.DLL.

ERR: Failed to complete setup of assembly (hr = 0x8007000b). Probing terminated.

[Former Member · Accepted solution]

Service Pack 9 for SAP Crystal Reports, developer version for Microsoft Visual Studio is now available for download. Don't forget that to integrate CRVS into VS IDE you must run the install exe(!). And yes, CRVS SP 9 does support VS 2013. List of fixes and Supported Platforms documentation coming next week.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

[Former Member]

There is no  version of CR that will work with VS 2013 - development or runtime. Copying files will definitely not work. Only option; wait for SP 9 - ETA, end of March.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

[Former Member]

Ludek,

I am not asking CR to work with VS2013, only that it not get in the way of the rest of the application.

I know this can happen because I run my application in debug using VS2013 without issue.  It works because I installed the run-time against my VS2010 installation prior to installing VS2013.  (incidentally, I am able to run the CR while debugging my application using VS2013, I just can't edit the reports)

Now, I want to duplicate that on the new workstations without getting a VS2010 license for each.

[Former Member]

Sorry, but I don't get it...

In your last post you say:

I am not asking CR to work with VS2013

In the initial post you say:

Where do I place the dlls so VS2013 can use them?

E.g.; If you are not asking CR to work with VS2013, why are you asking where to "place the dlls so VS2013 can use then"?

- Ludek

[Former Member]

I don't need the users to be able to review and edit the reports (generally, the primary purpose of installing the CR run-time files), I just want the program to be able to run in debug just like it is doing on my machine while I use VS2013.  They don't need to interact with anything related to CR, but it can't get in the way like it is right now.

If I can't make it work in this manner, I will have no choice but to remove CR from the system, and I really don't want to go through that headache.

[former_member11696]

Hi David,

Bottom line is CR does NOT integrate into the VS 2013 IDE period....

So only way to make your main app work is to copy your app and remove all references to CR Assemblies, then they can run your main app until you can integrate CR into VS 2013.

You could always try running the CR x86 Redist MSI package on those PC's, the app may work if it can at least find the CR runtime and not throw exceptions because it can't find them.

Don

[Former Member]

Where do I get that MSI?

[former_member11696]

Don