I'm using Visual Studio 2012 and working with .NET 4.0 C#.
I've downloaded and installed Crystal Reports developer version 13.0.7 (the latest service pack). When I include a reference to one of the DLLs, CrystalDecisions.Shared for example, the version in Properties in my Solution Explorer says 13.0.2000.0 (rather than 13.0.7.1136).
When adding the reference (Reference Manager>>Assemblies>>Extensions) if I click on the name then Visual Studio shows "Version" 13.0.2000.0 and "File Version" 13.0.7.1136.
Does anyone with Crystal Reports experience have ideas about this? I think everything's ok, but the version number is confusing me.
Thank you
When you installed CR, did you use the msi installer or the exe? It is important to use the exe on the development machine. Also, if you install a new version it is recommended to uninstall the old version.
Related
I'm coding one of my first projects in Visual Studio 2017 using the Microsoft Office Interop Tools to basically open some Word files, extract some content and export it to an XML file.
I know that on the target machine Office should be installed and actually on that PC a 2010 installation is licensed, while on my PC I have a 365 suite.
The first build was working only on my PC, with missing references errors to the interop library on the production PC, so I've downloaded the Microsoft Office 2010: Primary Interop Assemblies Redistributable
https://www.microsoft.com/en-us/download/details.aspx?id=3508 to include as a reference in my project, replacing the 2016 one.
First difficulty was: Once installed I cannot find the files on my drive, nor a reference inside visual studio, nor in the documentation. Is there any info about where to pick the dll?
So I unzipped from the cab the WORDPIA.DLL on an handy directory and referenced it in my project.
While is it working locally, it isn't yet on the production PC.
I'm sure I'm missing a lot of points on this topic, VS & C# are not my territory, but I need some tips to finish the project.
Go back to the original project (or reference the version of the PIAs installed on your machine). The redistributable is intended for installing to an Office 2010 machine where the PIAs were not installed. It's not meant to be used in the manner you envision.
Now click each "interop" reference entry and look at the Properties window. There should be a setting for "Embed Interop Types". Set that to True. This should make the project version-independent as it will contain the PIA information your project uses.
Note that "embed interop types" was introduced with .NET Framework 4.0 and is not available for earlier versions of the Framework. If an earlier version is a requirement, then you have to use late-binding or develop your project using Office 2010.
I have a project which has a crystal report which is been displayed on a winform. It runs perfectly on the project on Debug mood but once I create setup the crystal report area is totally not working and showing an error.
I'm using Crystal report 13 for Visual Studio 2013
After the error the system get close
Error Message
For your Crystal Reports Viewer to work on a target machine, you need to deploy the CrystalReports runtime with your installation.
For an overview what you need for which Version of CR have a look at this site:
Runtime Distributionand Supported Operating Systems
For the your version if you mean CR 2010 with "version 13.0" you need one of the runtimes from this site: http://scn.sap.com/docs/DOC-7824
EDIT
The "Solution" from my last comment should just show you what you could try.
Install the right runtime (see links above)
If your app is compiled as 32Bit you need the 32Bit runtime even on a 64 bit system
Add the runtime policy shown in the solution to your app.config
If you use an obfuscator you shouldnt encrypt strings
upgrade your crystal reports Libs to the latest servicepack
I have a C# application that requires .net version 4 in order to run. I know how to create a basic installer using the Visual Stuido Installer Setup Project that comes with Visual Studio and that installs my application fine, however, I can't get it to check if .net version 4 is already installed in the client machine and if not install it. Does anyone have any suggestions? Should I use a different approach besides this method? Purchasing a license for InstallShield is not an option as that is too expensive. Thanks
You should follow this guide on MSDN. It should tell you what you need to know about creating an installer to check for .NET 4.
The long and short of it is, if you set it as a prerequisite, the installer will check that it is installed.
On my dev system I VS 2010 installed, followed by the VS 2012 beta. I had to uninstall that at one point do to a confliction with CodeSmith and the .Net 4.5 Beta. It seems after that my dev systems is missing a few dlls and I specifically need the 'Microsoft.ReportViewer.DataVisualization.dll'. I've checked the 'C:\Windows\Microsoft.NET\assembly\GAC_MSIL' path and there is no 'Microsoft.ReportViewer.DataVisualization' folder. Is there any other way I can go about getting a copy of this dll?
Have a look in the windows SDK folder:
%PROGRAMFILES%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ReportViewer\ReportViewer.exe
It should install the required dll.
Edit
More information here.
I'm in a bit of trouble here. I upgraded one of our Winforms products from VS2008 to VS2010 about 4 weeks ago. The conversion was fine but we used Crystal Reports so had to install the VS2010 Crsytal Reports for Visual Studio 2010 Beta 2. This was fine and gave me the designer etc. back for crystal. I chose not to convert the reports when the solution opens so they are still setup for the original version of crystal.
We then continued with 4 weeks worth of development and now I come to do my first ClickOnce deploy under Vsiaul Studio 2010 and I'm having serious issues. ClickOnce Application files are set to having CrystalReports related modules as Prerequisites. I still want the end user to use the Crystal Reports for VS2008 rather than the runtime for 2010 which is ridiculously big and a beta.
When I publish the manifest is saying that the dependency for crystal is on version 14.0.2000.0 (VS2010 version of crystal report) but all the DLL references in the projects are set to use specific version and to point to 10.5.3700.0 (VS2008 version of crystal report). This means when trying to install from ClickOnce it fails saying:
"Unable to install or run the application The application requires that assembly CrystalDecisions.CrystalReports.Engine Version 14.0.2000.0 be installed in the Global Assembly Cache (GAC) first)"
I can't work out why the manifest is intent on using that version number given all the references are pointing to another version. If I bundle the VS2010 crystal runtimes that are beta into the ClickOnce deploy then the client gets the opposite error message saying that 10.5.3700.0 is required. If I install 10.5.3700.0 on the client they get a working system but I have to install the 10.5.3700.0 version manually and before that they've first had to endure an epic install of the 2010 runtime (14.0.2000.0) which doesn't even get used.
Essentially I am trying to get the manifest to say 10.5.3700.0 or figure out why VS2010 is intent on putting a newer version number in there.
Please help. Thanks
I converted the solution back to VS2008. Going back was relatively seamless. Since Crystal is in beta, the runtimes used to be ridiculously big, and I was losing large amounts of time on the ClickOnce deploys. The rollback solved all three.
I'm not happy about going back but the realities of using Crystal Reports in the year 2010 are pretty bad. I'll monitor progress from SAP as I know they are aiming to reduce runtimes this quarter and move out of beta.
Do you have the new CR stuff installed on your computer where you are building the application? If so, it's probably referencing the assemblies in the GAC.
You can try copying the assemblies you need into the project and setting the reference to point at the local copies, then on the reference set "copy local" to true. This will make sure it is referencing the local copies and not the ones in the GAC.
If that doesn't work, I would try copying the prerequisite for the previous version of Crystal Reports from the VS2008 folder to the VS2010 folder. You will find the packages here:
C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages (64-bit machine)
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages
Then close and reopen Visual Studio, and the old prerequisite should show up in VS and allow you to select it.