The MindFusion Forums

The MindFusion Forums
MindFusion.Reporting >> Bug Reports >> Compilation error https://mindfusion.eu/Forum/YaBB.pl?num=1260813206 Message started by Janice on Dec 14^th, 2009 at 5:53pm

Title: Compilation error
Post by Janice on Dec 14^th, 2009 at 5:53pm

I just installed the MindFusion.Diagramming software. However, whenever i compile it. An error occur. May i know how can i solve it? Thank a lot for help! :)

the error message is
"Exception occurred creating type 'MindFusion.Diagramming.Wpf.Diagram, MindFusion.Diagramming.Wpf, Version=2.2.1.21612, Culture=neutral, PublicKeyToken=1080b51628c81789' System.TypeLoadException: Could not load type 'System.Windows.Media.Effects.Effect' from assembly 'PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'."

Title: Re: Compilation error
Post by Stoyo on Dec 14^th, 2009 at 7:19pm

Hi,

It requires version 3.5 of the .NET runtime. If you have it, make sure the runtime target version in the project properties window is set to 3.5.

I hope that helps,
Stoyan

Title: Re: Compilation error
Post by Janice on Dec 15^th, 2009 at 3:23pm

Hi, Stoyan,

I'm using Microsoft visual studio 2008 with the microsoft .net framework version3.5. May i know how to check the runtime target version?

Thank you! :)

Title: Re: Compilation error
Post by Stoyo on Dec 15^th, 2009 at 4:04pm

Hi,

Right click the project in Solution explorer and select Properties. In the Application tab you can find a "Target Framework" drop down list that shows the available versions. Select .NET 3.5 and it should run fine. Is it some of the sample projects coming with the control that does not compile successfully?

Stoyan

Title: Re: Compilation error
Post by Janice on Dec 15^th, 2009 at 5:07pm

Hi,

My current "Target Framework" already in .NET 3.5, the problem still exists. By the way, I already try most of them, all having the same error message. :-[

Janice

Title: Re: Compilation error
Post by Stoyo on Dec 15^th, 2009 at 6:27pm

Now I wonder if this Effect class didn't appear in service pack 1 of the V3.5 runtime. Could you install .NET 3.5 SP1 and check if the problem persists?