I want to add crystal reports in application exe file when make installer of windows application on Visual Studio 2005. Like windows forms compile in exe file but crystal reports added in separate folder SMER But I don't want to add reports in SMER folder separate for security reasons.
What I have tried: When I change the Build Action of.rpt file to compile like Windows Forms Build Action and Build Installer, it's creating error. Unexpected character ' namespace does not directly contain members such as fields or methods. When answering a question please:. Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem.
Using Crystal Reports to Generate Reports from a Command Line. What we are doing here is creating a Crystal Report format that we wish to run to compile information for distribution to team members, etc. The zip file also contains information about the parameters you pass to the crexport.exe runtime engine. May 3, 2018 - What we are doing here is creating a Crystal Report format that we wish to. About the parameters you pass to the crexport.exe runtime engine.
Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
I just got a new system with Windows 8.1 and Visual Studio 2015 Enterprise. This system is the first in the office to have ONLY VS2015.
All other developer systems have had previous versions of VS installed. With the new system a project that references CRAXDRT (Crystal Reports ActiveX Designer Run Time Library 11.5) will no longer compile. The reference shows CRAXDRT as not available (little yellow warning icon over the reference). I tried removing the reference and re-adding it but as soon as I do it immediately shows up as invalid again. I have the Crystal Report development environment installed and have installed everything I can find that was different on my machine compared with other systems in the office under which the project will compile. I even went so far as to install VS2012 also but it is now failing builds even under that version of VS. Building the project that references CRAXDRT says 'failed build' but there are no errors in that project itself (errors only show up if I build projects that depend on the Crystal referencing project).
The output shows C: Program Files (x86) MSBuild 14.0 bin Microsoft.Common.CurrentVersion.targets(2398,5): warning MSB3283: Cannot find wrapper assembly for type library 'CRAXDRT'. I'm obviously missing some install somewhere but I have no idea what it is. I was able to find the cause of, and more importantly the solution to, this issue. The project in question was delay signed and the two new systems I tested on had not had signing verification turned off for the public key in question. It appears that something about the COM interop generation process doesn't like delay sign when the signing verification is still active (though projects without COM references compile just fine). A strange anomaly occurred when I was attempting to understand this issue.
I removed signing completely from the project and it suddenly compiled (that's when I realized the signing verification hadn't been removed). The strange piece is when I re-enabled the delay signing compiles continued to work and I've not been able to re-create the compile error again. It's like something got cached from the one successful compile (without delay sign) and then going back to delay signing uses this cached info. Quite strange. Hi Dane, I didn't find any documents about this problem for VS2015, actually I'm not quite sure if it supports VS2015, it's better to ask Crystal Report team for help, since Microsoft doesn't officially support this product. Try this SAP community: We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. Click to participate the survey. I don't believe this is an issue specifically with Crystal. I think there's something going on with how the COM interop is being generated (tlbimp.exe) with Visual Studio.
A new wrinkle in this is that I can create a new project of the same.NET version in VS2015, add a class library and then add a reference to the Crystal COM being discussed. That action does auto-generate the interop.
I've compared the.csproj sections for the COM reference in both projects and they're identical to what I included above. The question now becomes what could cause the auto-generation of interops to fail like that. It only occurs on machines that have VS2015 as their only version of VS. We have approximately three dozen developers who can all compile this project without issue but all they'er all using either VS2012 and/or VS2013.
I was able to find the cause of, and more importantly the solution to, this issue. The project in question was delay signed and the two new systems I tested on had not had signing verification turned off for the public key in question. It appears that something about the COM interop generation process doesn't like delay sign when the signing verification is still active (though projects without COM references compile just fine).
A strange anomaly occurred when I was attempting to understand this issue. I removed signing completely from the project and it suddenly compiled (that's when I realized the signing verification hadn't been removed).
The strange piece is when I re-enabled the delay signing compiles continued to work and I've not been able to re-create the compile error again. It's like something got cached from the one successful compile (without delay sign) and then going back to delay signing uses this cached info. Quite strange.