crystalreport runtime error

Question

0.00/5 (No votes)

See more:

hi i have an application that show this error to me when i send datatable to reportdocument!!!
please help...
error=
Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

my app.config file is:

XML

<?xml version="1.0"?>
<configuration>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
  </startup>
</configuration>

but i see this error!!!

Posted 21-Jul-12 2:33am

Alireza_Nasr

Updated 21-Jul-12 2:37am

Abdul Quader Mamun

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

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. 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.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandeep Mewara · Answer 1 · 2012-07-21T03:27:00

Solution 1

Based on the discussion here: mixed mode assembly is built against version '2.0.50727'[^], it, looks like your C# project references a C++/CLI project that has not yet been updated to .NET 4.0. Open your C++/CLI project in VS 2010 and build it again. And then make sure your C# project is referencing the new DLL and not the old one.

Posted 21-Jul-12 3:27am

Sandeep Mewara

Comments

Alireza_Nasr 21-Jul-12 10:04am

i do but i see that error...