cancel
Showing results for 
Search instead for 
Did you mean: 

Code analysis broken when using CR13

Former Member
0 Kudos

I have seen a number of posts about u201EBusinessObjects.Licensing.KeycodeDecoderu201C in this forum but none of them has a real solution and it seems that the situation of the error is different in every thread.

My problem is fairly simple to reproduce: I use VS2010 SP1 with CR 13.0.2 (SP2) with 64x runtime and all I do is create a new solution/project and add a blank report. Now as soon as I enter the project properties, Code Analysis and enable it by selecting the first checkbox I get the following warning when compiling:

MSBUILD : warning : CA0060 : The indirectly-referenced assembly 'BusinessObjects.Licensing.KeycodeDecoder, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' could not be found. This assembly is not required for analysis, however, analysis results could be incomplete. This assembly was referenced by: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet\CrystalDecisions.CrystalReports.Engine.dll.

I have reinstalled CR and I have no other version installed. I would not like to ignore the warning as Iu2019m looking for a proper solution here.

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

I don't have the Ultimate SKU of VS2010, but make sure you are using full framework 4.0, not the client.

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

0 Kudos

Just a side note. I was working with R&D on a 64 CR DB driver issue and they were using SP 2 and I did not see this problem happening.

It is only a Warning, it could be you simply need to turn the warning message Alerts down in VS, check the MS help file on how to.

Don

Answers (1)

Answers (1)

Former Member
0 Kudos

Thank you for your answers.

@Ludek: I am indeed building my solution for the .NET framework 3.5 but this is a customer requirement I cannot change at this time. I would expect that CR also supports this runtime as it is a default option of VS2010.

@Don: I tried to ignore the error by setting either an MSBuild parameter or an FxCop parameter but did not succeed so far. Anyway I don't feel ignoring/hiding an error message is a proper way of dealing with it.

Still I will close this post as it seems that it is more an FxCop problem and not a CR problem. I have found some posts in a VS forum where MS is asked to turn of the loading of assemblies that are referenced by assemblies referenced in a VS project (project A references assembly B which references assembly C -> C should be of no interest to FxCop when validating project A). As I think this is the problem here I qualify this as a VS/FxCop Bug and therefore close this thread.

0 Kudos

Hello,

What Ludek meant was CR does not support the Client Frame, 3.5 or 4.0, it must be the full version.

Since you are saying it's a VS problem then I'm marking as answered.

Thanks

Don