Scripting and .Net version

Title

Message

Confirm

No Yes

Confirm

Cancel Delete

<< Discussions Reply

NetMage

268 discussion posts

Will the .Net version be updated for scripting? I am trying to use a Linq function and it isn't supported.

May 21, 2015 • #1

At the moment we're kind of stuck on .NET 2 because we are reluctant to force customers to install .NET 4. However, we do want to switch DisplayFusion to .NET 4 as soon as we can, so rest assured that we will make the switch as soon as we think our customer base is ready for it

May 22, 2015 • #2

Any update on this? Possible to release a alternative build for those of us who can't do without Linq? Please

Mar 9, 2016 • #3

Not yet sorry. An alternative build isn't an option unfortunately

Mar 10, 2016 • #4

NetMage

268 discussion posts

v7.2 says it prefers .Net 4.0 now, but in Mar 2016 you said the scripting wasn't updated?

Now I want to use C# 6.0

Jul 20, 2016 (modified Jul 20, 2016) • #5

The newest DisplayFusion betas all run on .NET 4.x (4.6 if you have it installed). You should be able to use the new language features like Linq now.

https://www.displayfusion.com/Download/Beta/

Jul 21, 2016 • #6

NetMage

268 discussion posts

I have version 4.6 installed but when I attempted to use a C# 6.0 feature in a Scripted function, it did not work.

For example, string interpolation or extension functions found for collection initializers.

Jul 25, 2016 • #7

Sorry, I meant you'll be able to use the new language features like 4.x features compared to the older 2.x. Things like Linq, but not C# 6.0 features. Because it's compiled as a 4.0 application, the scripting is also limited to 4.0, even if it's technically running on 4.6.

Jul 26, 2016 • #8

NetMage

268 discussion posts

I attempted to use LINQ in the latest DisplayFusion, using the new Add .Net reference to add a reference to System.Linq, and I get an error message stating Linq doesn't exist in System?

Nov 1, 2021 • #9

@NetMage: Can you give me a sample of the Linq code you're trying to use? It could be an issue with the editor itself or the backend compiler, but once we have a sample we should be able to sort it out. Thanks!

Nov 4, 2021 • #10

Was this helpful?

(-)

<< Discussions Reply